Suggesting someone reinstall Windows because of a SID problem is irresponsible and wrong.
There is no need to reinstall Windows. Use a utility such as NEWSID and create a new SID rather than reinstall Windows.
You probably work much harder than you need, if this is your standard 'fix'. "Yeah, just reinstall Windows. That'll fix it".
Jeez.
Ace Fekay [MVP - Directory Services, MCT] wrote:
As others stated, that is indicative of identical SID symptoms.
26-Apr-10
As others stated, that is indicative of identical SID symptoms. M
suggestion is to make sure all files on the workstation are backed u
(if not using Redirection), and reinstall a fresh copy
Moving forward, put a copy of the Ghosted image on a workstaion, the
run Sysprep choosing Mini-setup, let it shut down and upon the machin
restarting it, trap the restart with a DOS bootable and Ghost th
image up to the shared location
Keep in mind, you need a VL copy of the operating system in order t
use one copy for deployment purposes. If you have a retail copy, yo
will need to have numerous Retail PIDs for each installation, whic
would not make sense to use. OEM copies do not work
Ace
Previous Posts In This Thread:
On Friday, April 23, 2010 3:15 PM
Bruce Sarte wrote:
Computer Account Not Found
Periodically in our Windows 2003 R2 AD implementation we have an issue wit
workstations that get this message when trying to login
I know you can simply rejoin them to the domain, and that work
swimmingly... But why does it happen?
On Saturday, April 24, 2010 5:53 AM
Meinolf Weber [MVP-DS] wrote:
Hello Bruce,This highly sounds that you are using imaged machines without
Hello Bruce
This highly sounds that you are using imaged machines without running syspre
on them. Please describe more details about the client installation
Best regard
Meinolf Webe
Disclaimer: This posting is provided "AS IS" with no warranties, and confer
no rights
** Please do NOT email, only reply to Newsgroup
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
On Saturday, April 24, 2010 8:17 AM
Bruce Sarte wrote:
Meinolf,Excellent suggestion. I do not do the imaging portion of deployment.
Meinolf
Excellent suggestion. I do not do the imaging portion of deployment.
know they are using ghost but do not know the details. I will look into it
Thanks
On 4/24/10 5:53 AM, in articl
, "Meinolf Weber [MVP-DS]"
On Sunday, April 25, 2010 4:46 PM
Ace Fekay [MVP - Directory Services, MCT] wrote:
Bruce,I agree with Meinolf.
Bruce
I agree with Meinolf. This appears to be a classic error message du
to identical machine SIDS. Even though a machine may have a differen
name, AD only uses the machine's SID
A sysprepped image upon first boot, will create a new identifier. I
the deployment team simply Ghosted a machine for imaging, then eac
machine will have identical SIDs, which will cause problems
Ac
This posting is provided "AS-IS" with no warranties or guarantees and confers no rights
Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution
Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 200
Microsoft Certified Traine
Microsoft MVP - Directory Service
If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
On Sunday, April 25, 2010 10:20 PM
Bruce Sarte wrote:
Sounds reasonable, the only question is what about a machine that has
Sounds reasonable, the only question is what about a machine that has worke
fine then all of a sudden shows this error? We seem to see this behavior,
machine will be fine then it just will not
On 4/25/10 4:46 PM, in article
"Ace Fekay [MVP - Directory Services, MCT]" <
wrote:
On Monday, April 26, 2010 4:59 AM
Hank Arnold wrote:
As Meinholf said, this is the nature of SIDs.
As Meinholf said, this is the nature of SIDs. They can seem to work for
a while and then stop. Something changed in the network/domain to
trigger it.
Simplest solution is to remove from the domain and then add back to the
domain.... I would wait for a few minutes for the update to propagate
before adding it back...
Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services
http://it.toolbox.com/blogs/personal-pc-assistant/
On 4/25/2010 10:20 PM, Bruce Sarte wrote:
On Monday, April 26, 2010 1:03 PM
Ace Fekay [MVP - Directory Services, MCT] wrote:
As others stated, that is indicative of identical SID symptoms.
As others stated, that is indicative of identical SID symptoms. My
suggestion is to make sure all files on the workstation are backed up
(if not using Redirection), and reinstall a fresh copy.
Moving forward, put a copy of the Ghosted image on a workstaion, then
run Sysprep choosing Mini-setup, let it shut down and upon the machine
restarting it, trap the restart with a DOS bootable and Ghost the
image up to the shared location.
Keep in mind, you need a VL copy of the operating system in order to
use one copy for deployment purposes. If you have a retail copy, you
will need to have numerous Retail PIDs for each installation, which
would not make sense to use. OEM copies do not work.
Ace
Submitted via EggHeadCafe - Software Developer Portal of Choice
WPF Control?s Default Style or Template by Extending the WPF Designer in Visual Studio 2010
http://www.eggheadcafe.com/tutorials...udio-2010.aspx
Similar Threads
Linear Mode
