Re: WSUS Clients Won't Register

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Hello AndyTC@xxxxxxxxxxxxxxxx,

Software is not effected by sysprep. See here whats going on:
http://technet.microsoft.com/en-us/library/cc736393(WS.10).aspx#w2k3tr_sys_how_pqxl

Choose "Sysprep Processes and Interactions"

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


Hello,

Will running sysprep mess/screw up with any of the software installed
on the laptop?

What about all the users that have logged on already, will it messed
with their cached local profiles, etc?

Meinolf Weber [MVP-DS] wrote:

Hello AndyTC@xxxxxxxxxxxxxxxx,

Yes, move it from the domain to workgroup and delete the account in
AD UC. Then use sysprep to change the SIDs and join it back to the
domain. If you think about using NewSID from sysinternals, keep in
mind that this is not supported from MS. Also NewSID will ONLY change
the SID, while sysprep will change some more settings.

See here about preparing an image for duplication:
http://technet.microsoft.com/en-us/library/bb457067.aspx

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Ahh you are probably right.

One question, will running change-sid program screw up with the
active directory computer object then?

Cleve S. wrote:

Andy,

Just a guess here, are the laptops from a common image? If you
used imaging software to clone the laptops and didn't use SysPrep
to change the SID you'll have trouble with WSUS. WSUS sees 1 SID &
thinks it's the same laptop.

Cleve S.

<AndyTC@xxxxxxxxxxxxxxxx> wrote in message
news:u5e$br64JHA.1716@xxxxxxxxxxxxxxxxxxxxxxx
Hello,

I recently setup WSUS SP1 in a 2003 AD environment.
I have a weird problem; All my servers registered as I did those
manually
on the local GP.
I created a GP for all the laptops on this site to point to the
WSUS
server.
However, only one laptop has registered.
But here is the weird part - It seems to change every few hours.
The one laptop that is registered will keep changing names to
different
laptops.
It's like it's only allowing one to register, and it replaces that
one
with a new one when it registers.
Any ideas?
I ran clientdiag.exe on a few laptops and it passed all connection
tests to the WSUS server.



.



Relevant Pages

  • Re: Sysprep on a Vista Rollback to XP forces reactivation
    ... Thanks Dave - Sorry for not replying sooner but its been madness over here. ... We have 50 laptops to roll out in my organisation. ... We sysprep it using latest version of sysprep ... We do not have any XP product keys anyway - but do have the XP ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Imagining/Cloning Desktops
    ... HP desktops, laptops, and servers for the company. ... set the power options the way I want them to disable Standby and Sleep ... mode before I copy the profile to Default User and sysprep, ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Imagining/Cloning Desktops
    ... HP desktops, laptops, and servers for the company. ... set the power options the way I want them to disable Standby and Sleep ... mode before I copy the profile to Default User and sysprep, ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: WSUS Clients Wont Register
    ... Then use sysprep to change the SIDs and join it back to the domain. ... are the laptops from a common image? ... change the SID you'll have trouble with WSUS. ... It's like it's only allowing one to register, ...
    (microsoft.public.windows.server.general)
  • Re: Sysprep on a Vista Rollback to XP forces reactivation
    ... We have 50 laptops to roll out in my organisation. ... Vista OEM machines that have been rolled back for us in the factory to ... We sysprep it using latest version of sysprep ... We do not have any XP product keys anyway - but do have the XP ...
    (microsoft.public.windowsxp.setup_deployment)