sys6x Posted April 23, 2007 Share Posted April 23, 2007 Hi,Is there a command that I could type on a new client computer in order to get WSUS to list the computer in its database, manually? Because it looks like it's doing this only when the scheduled WSUS sync task is running...Also, I wonder if all my computer have the same SID...does this cause any problem with WSUS?Thanks Link to comment Share on other sites More sharing options...
nmX.Memnoch Posted April 23, 2007 Share Posted April 23, 2007 Run the following in the client:wuauclt.exe /detectnowBTW, this information is available in the WSUS Operations Guide. Link to comment Share on other sites More sharing options...
sys6x Posted April 23, 2007 Author Share Posted April 23, 2007 Thanks for the reply.I tried that but it's not doing anything except running the process... Link to comment Share on other sites More sharing options...
nmX.Memnoch Posted April 23, 2007 Share Posted April 23, 2007 You may need to update the AU client on the workstation. What OS is the workstation running? Link to comment Share on other sites More sharing options...
sys6x Posted April 24, 2007 Author Share Posted April 24, 2007 It's on XPSP2 ProI've been told that scheduling the updates with a GPO disables the possibility of a manual update...dunno if it's true Link to comment Share on other sites More sharing options...
eyeball Posted April 24, 2007 Share Posted April 24, 2007 if its a single pc then you need to go into the registry and point it to your WSUS server.i cant remember where the key is though :S but when i had trouble with wsus adding this key and rebooting did the trick Link to comment Share on other sites More sharing options...
nmX.Memnoch Posted April 24, 2007 Share Posted April 24, 2007 If you're in a domain it's best to use a GPO for this. Otherwise...yeah, you have to manually edit the registry on the client to tell it to point to the WSUS server for updates.Also, I wonder if all my computer have the same SID...does this cause any problem with WSUS?Yes, it very well could cause issues with WSUS...plus A LOT more. I'm going to assume you imaged all of the machines without using SysPrep? Link to comment Share on other sites More sharing options...
sys6x Posted April 25, 2007 Author Share Posted April 25, 2007 Yeah, you're assuming right..no idea what is sysprep for.. I think I found out, either it's removing the setup that says "put this computer in this group" in gpedit.msc or it's changing the SID that did effect... I will see when trying to deploy another computer Link to comment Share on other sites More sharing options...
nmX.Memnoch Posted April 25, 2007 Share Posted April 25, 2007 You really need to look into sysprep. Having every machine with the same SID can cause some serious headaches. The downside is that you'll have to drop them from the domain to run sysprep and then rejoin them after running sysprep. Before rejoining the computer account in the domain will need to be reset.The latest version of sysprep is included in the XP SP2 Deployment Tools. Link to comment Share on other sites More sharing options...
sys6x Posted April 25, 2007 Author Share Posted April 25, 2007 Well it isn't deployed yet, I'm still at the stage to work on the images! So it should be something like running sysprep on the actual image computer and then I can image itI'll check out that sysprep thing, thanks Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now