Re: Ghosting Win 2003 -- Can't log-in
From: Pegasus \(MVP\) (I.can_at_fly.com)
Date: 02/12/05
- Next message: monk: "Map drives using Run-As"
- Previous message: Craig York: "Users updating account information"
- In reply to: Paul Mathieu: "Re: Ghosting Win 2003 -- Can't log-in"
- Next in thread: Paul Mathieu: "Re: Ghosting Win 2003 -- Can't log-in"
- Reply: Paul Mathieu: "Re: Ghosting Win 2003 -- Can't log-in"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 13 Feb 2005 08:14:12 +1100
"Paul Mathieu" <afs_solutions@yahoo.ca> wrote in message
news:6a03f23.0502120856.333a30f1@posting.google.com...
> "Pegasus \(MVP\)" <I.can@fly.com> wrote in message
news:<uA2BBGLEFHA.1296@TK2MSFTNGP10.phx.gbl>...
> > "Paul Mathieu" <afs_solutions@yahoo.ca> wrote in message
> > news:6a03f23.0502111819.579c904e@posting.google.com...
> > > Today I decided to back-up my W2K3 Server image using Ghost 2002
> > > (ghostpe.exe). I went from a 120Gb Drive down to an 80Gb drive.
> > > Ghost re-sized the partitions and the image transfered without any
> > > errors. That is, until I tested the image on the 80Gb and found that
> > > I couldn't log-in. The server would boot normally, give me the log-on
> > > prompt, but as soon as I'd log-in it would bring me right back to the
> > > log-on screen -- Same test done in Safe Mode with the same result.
> > >
> > > I've completed this procedure with W2K Server on the same computer and
> > > everything worked fine. Just wondering if there is some odd "copy
> > > protection" going on with W2K3 Server that prevents a person from
> > > imaging their drive. Seems weird if so... I'm acustomed to imaging
> > > servers before making heavy configuration changes, just in case
> > > something doesn't go as planned.
> > >
> > > If anyone has an idea to what's happening, please drop a line back.
> > >
> > > Thanks,
> > >
> > > Paul
> >
> > This is a fairly common problem, often observed after some
> > cloning action. It is most likely caused by your system drive
> > letter now being something other than C:.
> >
> > The actual remedy depends on the facilities you have, e.g.
> > - Is the machine networked?
> > - Do you have another Win2000/XP PC available?
> > - Do you have a Bart PE boot CD available?
>
> Yes, to all three questions. It's networked via a 802.11b USB but has
> no clients logging into it, yet. I have both another XP and a Win2K3
> machine operational. In regards to the "Bart PE CD"; not sure if what
> I have is that one specifically.. I've just got them labled as WinPE
> and Super WinPE.. Well, you've captivated my attention.. Awaiting
> your feedback. Thanks..
Since the machine is networked, you can fix the problem by
doing this on some networked Win2000/XP PC where you
are logged on with an admin account that is also an admin
account on the server:
1. Run the commands
psexec \\YourServer cmd
set SystemDrive
Make a note of the system drive letter. It is probably not drive C:.
2. Run regedit and open the server registry.
3. Navigate to HKLM\SYSTEM\MountedDevices.
4. Rename the value DosDevices\X: to DosDevices\C:
(where X: is the drive letter you noted in Step 1).
If you already have a value DosDevices\C:, rename it to something else.
5. Navigate to HKLM/Software/Microsoft/Windows NT/Current Version/
Winlogon/Userinit and make sure that it points to drive C:.
6. Navigate to HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management
and make sure that it points to drive C:.
You can obtain psexec.exe from www.sysinternals.com.
If you have a Bart PE boot CD then you can edit the registry
of the problem server in much the same way.
- Next message: monk: "Map drives using Run-As"
- Previous message: Craig York: "Users updating account information"
- In reply to: Paul Mathieu: "Re: Ghosting Win 2003 -- Can't log-in"
- Next in thread: Paul Mathieu: "Re: Ghosting Win 2003 -- Can't log-in"
- Reply: Paul Mathieu: "Re: Ghosting Win 2003 -- Can't log-in"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
