T
Tom Penharston
Here's a problem that I never dreamed of.
I have several legacy machines that were deployed without sysprep. At
the time there was no benefit to sealing the images. There was no
Active Directory for these machines to join, workgroup connectivity
worked just fine without a unique SID, and if we really wanted to
change the SID for some reason, then we could always run ghstwalk from
Symantec Ghost. I had no problem for years. Most of the images were
replaced every few months so I had no worries about long term problems.
This was the most efficient deployment we found, 'no sysprep' means
less customization. Even regarding product keys, we had a site licence
for an upgrade, so there was no reason to enter unique keys for each
machine.
Sysprep was always on the horizon. None-the-less, I couldn't justify
the extra process and the extra time during customization. Many of
these deployments were done under presure. Certan - heavy use -
clients were being re-imaged on a weekly basis during a short
maintenance opening.
Unfortunately, not all of the machines were temporary. Some machines
went to permanent use and have been like this for a couple of years.
Recently, I wanted to inventory the legacy machines in WSUS.
If you've never had the pleasure of using WSUS to monitor clients with
the same SID, well this is what it looks like to me; the clients appear
as one computer to the WSUS, only the computer name changes several
times daily.
Clearly I had to change the SID on each client to get useful
information in WSUS. I ran a test case with two identical XP test
clients. By using ghstwalk I achieved exactly what I wanted. There
were no obvious problems. I was ready to go 'live'.
Then I designated three of my legacy clients for ghstwalk, one with W2K
and two with XP. The clients were renamed and given new SIDs. All
went well.
Users called me a day later, Outlook Express produced errors. Mail was
eventually accessible but they endured:
"...Server response "Logon failure" unknown user name or bad password",
Port 143; Secure(SSL): No, Error Number: 0x800C006F"
OE would no longer save passwords. On the W2K machine the 'Save
Password' check box was greyed out. I tried the prescribed Microsoft
Technet registry fix for Protected Storage System Provider, but it
failed to work.
Please advise. Thanks for taking an interest.
-Tom
I have several legacy machines that were deployed without sysprep. At
the time there was no benefit to sealing the images. There was no
Active Directory for these machines to join, workgroup connectivity
worked just fine without a unique SID, and if we really wanted to
change the SID for some reason, then we could always run ghstwalk from
Symantec Ghost. I had no problem for years. Most of the images were
replaced every few months so I had no worries about long term problems.
This was the most efficient deployment we found, 'no sysprep' means
less customization. Even regarding product keys, we had a site licence
for an upgrade, so there was no reason to enter unique keys for each
machine.
Sysprep was always on the horizon. None-the-less, I couldn't justify
the extra process and the extra time during customization. Many of
these deployments were done under presure. Certan - heavy use -
clients were being re-imaged on a weekly basis during a short
maintenance opening.
Unfortunately, not all of the machines were temporary. Some machines
went to permanent use and have been like this for a couple of years.
Recently, I wanted to inventory the legacy machines in WSUS.
If you've never had the pleasure of using WSUS to monitor clients with
the same SID, well this is what it looks like to me; the clients appear
as one computer to the WSUS, only the computer name changes several
times daily.
Clearly I had to change the SID on each client to get useful
information in WSUS. I ran a test case with two identical XP test
clients. By using ghstwalk I achieved exactly what I wanted. There
were no obvious problems. I was ready to go 'live'.
Then I designated three of my legacy clients for ghstwalk, one with W2K
and two with XP. The clients were renamed and given new SIDs. All
went well.
Users called me a day later, Outlook Express produced errors. Mail was
eventually accessible but they endured:
"...Server response "Logon failure" unknown user name or bad password",
Port 143; Secure(SSL): No, Error Number: 0x800C006F"
OE would no longer save passwords. On the W2K machine the 'Save
Password' check box was greyed out. I tried the prescribed Microsoft
Technet registry fix for Protected Storage System Provider, but it
failed to work.
Please advise. Thanks for taking an interest.
-Tom