anyweb

its better to fix the problem you have now first that way you'll learn, there'll be plenty of opportunities to reinstall labs in the future startup Active directory users and computers and make the user you are installing/configuring sccm with a domain administrator this is not the way you should do it in production, but will be ok for a lab

We had two new Knowledge Base articles on System Center Configuration Manager 2007 last week: They’re both about an issue where the image capture process may fail during the "Prepare Windows for Capture" stage but the first refers to ConfigMgr 2007 RTM and the second refers to ConfigMgr 2007 SP1. Note that the hotfixes mentioned are different depending on the version you’re running as well. The links and titles are below: ======== KB969991 - When you use System Center Configuration Manager 2007 RTM to capture an image of Windows Vista SP2 or of Windows Server 2008 SP2, the image capture process fails during the "Prepare Windows for Capture" stage KB970093 - When you use System Center Configuration Manager 2007 Service Pack 1 to capture an image of Windows Vista SP2 or of Windows Server 2008 SP2, the image capture process fails during the "Prepare Windows for Capture" stage source > http://blogs.technet.com/configurationmgr/...06-13-2009.aspx

please look at this post, is it the same as your problem ? http://www.myitforum.com/forums/SOLVED_%2D...m_203392/tm.htm

where exactly are you trying to add this custom.corp.mydomain.com info to ?

give me a download link for the driver you tried please

I'm not quite following you, why would you want to change the Active Directory domain ?

how was SCCM installed in your environment, was it an upgrade or clean install ? is remote desktop the only issue you are seeing ? what is the state of your Site Status and the componets in there ?

and the user you used to setup SCCM with, is that the same user you installed WSUS with ?

interesting problem, netbios names are limited to 16 characters(Microsoft limits a NetBIOS name to be 15 characters in lenght and uses the 16th character as the NetBIOS suffix), is this post the same as your problem ? if so, you'll have to have unique NETBIOS names across your organisation

no worries, while you are waiting look at this post about installing drivers (application based drivers) to specific hardware and this one for installing drivers the 'normal' way via task sequences, its vista based but change everything vista for xp.

ok so is WSUS running on the SAME server as SCCM please clarify

you are thinking correctly you can add drivers to images in the task sequence, if you can post your SMSTS.log file here I will be able to see why it ignored your drivers cheers anyweb

heres your problem so does the SCCM computer account have administrative priveledges on the WSUS server ? please double check the guide. cheers anyweb

try asking on their dedicated support forums then, here http://www.wilderssecurity.com/forumdisplay.php?f=64

what is between your sccm server and the client you are testing with ? on the client, have you tried doing an nslookup test ?

it's closed for now, sorry

is your management point the same as the one listed ?

if deploying firefox fails then you have done something wrong from the beginning. was this a brand new install or a re-done install ? are the active directory boundaries correct ???

on any of your clients can you show me the configmgr client screenshot of the General Tab

look here

glad you found a solution and thanks for giving the feedback moving this thread to Reporting cheers anyweb

have you read the documentation for the product ? maybe it's in there

kick off a Data Discovery cycle and see what happens

verify the package exists and if it does distribute it to the dp again if that fails, delete the package from the dp, then delete the package, then recreate it, then redistribute it to a DP or DP(s)

you can do software updates with wsus, or with sccm, not both, sccm will control wsus once you set it up that way, your system status logs in ConfigMgr admin console should give you some ideas as to why its failing (look for the wsus logs)