Automaticcly logged off the moment I login in on the DC using any account

[Guest NoSpam Man]

Hi,

 

I have added an external eSATA drive to my server which I wanted to install

vista onto. The idea was I could shut down w2003 server, plug in the

external eSATA drive, change the BIOS to put this external drive as the

first boot drive, and boot up vista. I would also be able to remove this

drive, boot up and go back into W2003 server.

 

So I setup the bios as above, with the eSATA drive plugged in, booted up

installed Vista onto the external drive, and it works fine.

 

Problem is that now there is a problem with the W2003 server.

 

It boots with 'service failed to start.......) message, and goes to the

login screen, but when I log in to the server it logs me off and back to the

login screen. Even with the Administrator login, the same occurs, so I am

locked out. When I use RDC to login in, the login processes and then the

RDC is closed.

 

I can access the server (\\server\\D$) and other services, however what was

the C$ seems to now be the F$. For some reason its changed my old C$ to F$

(the external eSATA is not plugged in)

 

I can also access the event log on the server from another machine, and I

can see the following two error in the log.

 

Any idea what I can do to resolve this????

 

--

Windows cannot query for the list of Group Policy objects. Check the event

log for possible messages previously logged by the policy engine that

describes the reason for this.

 

---

Windows cannot access the file gpt.ini for GPO

CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=chelsea,DC=local.

The file must be present at the location

<\\chelsea.local\sysvol\chelsea.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>.

(Configuration information could not be read from the domain controller,

either because the machine is unavailable, or access has been denied. ).

Group Policy processing aborted.

[Guest Pegasus \(MVP\)]

Re: Automaticcly logged off the moment I login in on the DC using any account

 

 

"NoSpam Man" <nospam@nospam.com> wrote in message

news:uJM6loRIJHA.4836@TK2MSFTNGP03.phx.gbl...

> Hi,

>

> I have added an external eSATA drive to my server which I wanted to

> install vista onto. The idea was I could shut down w2003 server, plug in

> the external eSATA drive, change the BIOS to put this external drive as

> the first boot drive, and boot up vista. I would also be able to remove

> this drive, boot up and go back into W2003 server.

>

> So I setup the bios as above, with the eSATA drive plugged in, booted up

> installed Vista onto the external drive, and it works fine.

>

> Problem is that now there is a problem with the W2003 server.

>

> It boots with 'service failed to start.......) message, and goes to the

> login screen, but when I log in to the server it logs me off and back to

> the login screen. Even with the Administrator login, the same occurs, so I

> am locked out. When I use RDC to login in, the login processes and then

> the RDC is closed.

>

> I can access the server (\\server\\D$) and other services, however what

> was the C$ seems to now be the F$. For some reason its changed my old C$

> to F$ (the external eSATA is not plugged in)

>

> I can also access the event log on the server from another machine, and I

> can see the following two error in the log.

>

> Any idea what I can do to resolve this????

>

> --

> Windows cannot query for the list of Group Policy objects. Check the event

> log for possible messages previously logged by the policy engine that

> describes the reason for this.

>

> ---

> Windows cannot access the file gpt.ini for GPO

> CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=chelsea,DC=local.

> The file must be present at the location

> <\\chelsea.local\sysvol\chelsea.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>.

> (Configuration information could not be read from the domain controller,

> either because the machine is unavailable, or access has been denied. ).

> Group Policy processing aborted.

>

 

This one is easily solved. Open the server's registry from a networked

machine, then do this:

1. Navigate to HKLM\SYSTEM\MountedDevices

2. Rename \DosDevices\F: to DosDevices\C:.

3. Reboot the machine with shutdown.exe.

If there is already a DosDevices\C:, rename it to DosDevices\X:.

[Guest NoSpam Man]

Re: Automaticcly logged off the moment I login in on the DC using any account

 

HI,

Thanks for you answer..

 

Where do I find the directory HKLM

 

I can not see it under the \windows\system or system32

 

 

"Pegasus (MVP)" <I.can@fly.com.oz> wrote in message

news:%23HtmzzSIJHA.4280@TK2MSFTNGP04.phx.gbl...

>

> "NoSpam Man" <nospam@nospam.com> wrote in message

> news:uJM6loRIJHA.4836@TK2MSFTNGP03.phx.gbl...

>> Hi,

>>

>> I have added an external eSATA drive to my server which I wanted to

>> install vista onto. The idea was I could shut down w2003 server, plug in

>> the external eSATA drive, change the BIOS to put this external drive as

>> the first boot drive, and boot up vista. I would also be able to remove

>> this drive, boot up and go back into W2003 server.

>>

>> So I setup the bios as above, with the eSATA drive plugged in, booted up

>> installed Vista onto the external drive, and it works fine.

>>

>> Problem is that now there is a problem with the W2003 server.

>>

>> It boots with 'service failed to start.......) message, and goes to the

>> login screen, but when I log in to the server it logs me off and back to

>> the login screen. Even with the Administrator login, the same occurs, so

>> I am locked out. When I use RDC to login in, the login processes and

>> then the RDC is closed.

>>

>> I can access the server (\\server\\D$) and other services, however what

>> was the C$ seems to now be the F$. For some reason its changed my old C$

>> to F$ (the external eSATA is not plugged in)

>>

>> I can also access the event log on the server from another machine, and I

>> can see the following two error in the log.

>>

>> Any idea what I can do to resolve this????

>>

>> --

>> Windows cannot query for the list of Group Policy objects. Check the

>> event log for possible messages previously logged by the policy engine

>> that describes the reason for this.

>>

>> ---

>> Windows cannot access the file gpt.ini for GPO

>> CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=chelsea,DC=local.

>> The file must be present at the location

>> <\\chelsea.local\sysvol\chelsea.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>.

>> (Configuration information could not be read from the domain controller,

>> either because the machine is unavailable, or access has been denied. ).

>> Group Policy processing aborted.

>>

>

> This one is easily solved. Open the server's registry from a networked

> machine, then do this:

> 1. Navigate to HKLM\SYSTEM\MountedDevices

> 2. Rename \DosDevices\F: to DosDevices\C:.

> 3. Reboot the machine with shutdown.exe.

> If there is already a DosDevices\C:, rename it to DosDevices\X:.

>

>

[Guest Pegasus \(MVP\)]

Re: Automaticcly logged off the moment I login in on the DC using any account

 

HKLM is not a file; it is the H_Key_Local_Machine registry hive. That's why

I suggested you should open the server's registry. You do it with

regedit.exe.

 

"NoSpam Man" <nospam@nospam.com> wrote in message

news:O$M6CMUIJHA.1160@TK2MSFTNGP04.phx.gbl...

> HI,

> Thanks for you answer..

>

> Where do I find the directory HKLM

>

> I can not see it under the \windows\system or system32

>

>

> "Pegasus (MVP)" <I.can@fly.com.oz> wrote in message

> news:%23HtmzzSIJHA.4280@TK2MSFTNGP04.phx.gbl...

>>

>> "NoSpam Man" <nospam@nospam.com> wrote in message

>> news:uJM6loRIJHA.4836@TK2MSFTNGP03.phx.gbl...

>>> Hi,

>>>

>>> I have added an external eSATA drive to my server which I wanted to

>>> install vista onto. The idea was I could shut down w2003 server, plug in

>>> the external eSATA drive, change the BIOS to put this external drive as

>>> the first boot drive, and boot up vista. I would also be able to remove

>>> this drive, boot up and go back into W2003 server.

>>>

>>> So I setup the bios as above, with the eSATA drive plugged in, booted up

>>> installed Vista onto the external drive, and it works fine.

>>>

>>> Problem is that now there is a problem with the W2003 server.

>>>

>>> It boots with 'service failed to start.......) message, and goes to the

>>> login screen, but when I log in to the server it logs me off and back to

>>> the login screen. Even with the Administrator login, the same occurs, so

>>> I am locked out. When I use RDC to login in, the login processes and

>>> then the RDC is closed.

>>>

>>> I can access the server (\\server\\D$) and other services, however what

>>> was the C$ seems to now be the F$. For some reason its changed my old C$

>>> to F$ (the external eSATA is not plugged in)

>>>

>>> I can also access the event log on the server from another machine, and

>>> I can see the following two error in the log.

>>>

>>> Any idea what I can do to resolve this????

>>>

>>> --

>>> Windows cannot query for the list of Group Policy objects. Check the

>>> event log for possible messages previously logged by the policy engine

>>> that describes the reason for this.

>>>

>>> ---

>>> Windows cannot access the file gpt.ini for GPO

>>> CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=chelsea,DC=local.

>>> The file must be present at the location

>>> <\\chelsea.local\sysvol\chelsea.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>.

>>> (Configuration information could not be read from the domain controller,

>>> either because the machine is unavailable, or access has been denied. ).

>>> Group Policy processing aborted.

>>>

>>

>> This one is easily solved. Open the server's registry from a networked

>> machine, then do this:

>> 1. Navigate to HKLM\SYSTEM\MountedDevices

>> 2. Rename \DosDevices\F: to DosDevices\C:.

>> 3. Reboot the machine with shutdown.exe.

>> If there is already a DosDevices\C:, rename it to DosDevices\X:.

>>

>>

>

[Guest Dave Patrick]

Re: Automaticcly logged off the moment I login in on the DC using any account

 

These articles may help.

 

http://support.microsoft.com/kb/249321

http://support.microsoft.com/kb/223188/

 

 

--

 

Regards,

 

Dave Patrick ....Please no email replies - reply in newsgroup.

Microsoft Certified Professional

Microsoft MVP [Windows]

http://www.microsoft.com/protect

 

 

"NoSpam Man" wrote:

> Hi,

>

> I have added an external eSATA drive to my server which I wanted to

> install vista onto. The idea was I could shut down w2003 server, plug in

> the external eSATA drive, change the BIOS to put this external drive as

> the first boot drive, and boot up vista. I would also be able to remove

> this drive, boot up and go back into W2003 server.

>

> So I setup the bios as above, with the eSATA drive plugged in, booted up

> installed Vista onto the external drive, and it works fine.

>

> Problem is that now there is a problem with the W2003 server.

>

> It boots with 'service failed to start.......) message, and goes to the

> login screen, but when I log in to the server it logs me off and back to

> the login screen. Even with the Administrator login, the same occurs, so I

> am locked out. When I use RDC to login in, the login processes and then

> the RDC is closed.

>

> I can access the server (\\server\\D$) and other services, however what

> was the C$ seems to now be the F$. For some reason its changed my old C$

> to F$ (the external eSATA is not plugged in)

>

> I can also access the event log on the server from another machine, and I

> can see the following two error in the log.

>

> Any idea what I can do to resolve this????

>

> --

> Windows cannot query for the list of Group Policy objects. Check the event

> log for possible messages previously logged by the policy engine that

> describes the reason for this.

>

> ---

> Windows cannot access the file gpt.ini for GPO

> CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=chelsea,DC=local.

> The file must be present at the location

> <\\chelsea.local\sysvol\chelsea.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>.

> (Configuration information could not be read from the domain controller,

> either because the machine is unavailable, or access has been denied. ).

> Group Policy processing aborted.

>

>

>

>

>

[Guest NoSpam Man]

Re: Automaticcly logged off the moment I login in on the DC using any account

 

Hi...

 

Thanks for your reply.

 

Using a vista machine I start the regedit and connect to the network

register for the server.

 

I am able to connect find the setting and do as you suggest.

 

I can close regedit, and reopen it, and see that the setting is now set to

C:

 

However when I reboot the server, it is somehow reset to be the F: and the

C: is setting is gone.

 

Any idea on what is happening ?

 

Thanks

 

 

 

"Pegasus (MVP)" <I.can@fly.com.oz> wrote in message

news:OEf4whUIJHA.1160@TK2MSFTNGP04.phx.gbl...

> HKLM is not a file; it is the H_Key_Local_Machine registry hive. That's

> why I suggested you should open the server's registry. You do it with

> regedit.exe.

>

> "NoSpam Man" <nospam@nospam.com> wrote in message

> news:O$M6CMUIJHA.1160@TK2MSFTNGP04.phx.gbl...

>> HI,

>> Thanks for you answer..

>>

>> Where do I find the directory HKLM

>>

>> I can not see it under the \windows\system or system32

>>

>>

>> "Pegasus (MVP)" <I.can@fly.com.oz> wrote in message

>> news:%23HtmzzSIJHA.4280@TK2MSFTNGP04.phx.gbl...

>>>

>>> "NoSpam Man" <nospam@nospam.com> wrote in message

>>> news:uJM6loRIJHA.4836@TK2MSFTNGP03.phx.gbl...

>>>> Hi,

>>>>

>>>> I have added an external eSATA drive to my server which I wanted to

>>>> install vista onto. The idea was I could shut down w2003 server, plug

>>>> in the external eSATA drive, change the BIOS to put this external drive

>>>> as the first boot drive, and boot up vista. I would also be able to

>>>> remove this drive, boot up and go back into W2003 server.

>>>>

>>>> So I setup the bios as above, with the eSATA drive plugged in, booted

>>>> up installed Vista onto the external drive, and it works fine.

>>>>

>>>> Problem is that now there is a problem with the W2003 server.

>>>>

>>>> It boots with 'service failed to start.......) message, and goes to the

>>>> login screen, but when I log in to the server it logs me off and back

>>>> to the login screen. Even with the Administrator login, the same

>>>> occurs, so I am locked out. When I use RDC to login in, the login

>>>> processes and then the RDC is closed.

>>>>

>>>> I can access the server (\\server\\D$) and other services, however what

>>>> was the C$ seems to now be the F$. For some reason its changed my old

>>>> C$ to F$ (the external eSATA is not plugged in)

>>>>

>>>> I can also access the event log on the server from another machine, and

>>>> I can see the following two error in the log.

>>>>

>>>> Any idea what I can do to resolve this????

>>>>

>>>> --

>>>> Windows cannot query for the list of Group Policy objects. Check the

>>>> event log for possible messages previously logged by the policy engine

>>>> that describes the reason for this.

>>>>

>>>> ---

>>>> Windows cannot access the file gpt.ini for GPO

>>>> CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=chelsea,DC=local.

>>>> The file must be present at the location

>>>> <\\chelsea.local\sysvol\chelsea.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>.

>>>> (Configuration information could not be read from the domain

>>>> controller, either because the machine is unavailable, or access has

>>>> been denied. ). Group Policy processing aborted.

>>>>

>>>

>>> This one is easily solved. Open the server's registry from a networked

>>> machine, then do this:

>>> 1. Navigate to HKLM\SYSTEM\MountedDevices

>>> 2. Rename \DosDevices\F: to DosDevices\C:.

>>> 3. Reboot the machine with shutdown.exe.

>>> If there is already a DosDevices\C:, rename it to DosDevices\X:.

>>>

>>>

>>

>

>

[Guest NoSpam Man]

Re: Automaticcly logged off the moment I login in on the DC using any account

 

Hi

Thanks for your reply.

 

I followed these instructions, and the mounted device was wrong, so I

renamed it.

 

I rebooted the machine, but it put back the mounted device to be the wrong

letter again somehow.

 

I tried again, checked my permission, and reset the value. I was also able

to restart regedit and could see that my edit to correct the mounted device

was saved. Yet again when I rebooted it puts the C drive to be the G drive

and the problem is still there.

 

Is there something else that could be done to solve this?

 

Thanks

 

"Dave Patrick" <DSPatrick@nospam.gmail.com> wrote in message

news:e7qCh4WIJHA.1156@TK2MSFTNGP04.phx.gbl...

> These articles may help.

>

> http://support.microsoft.com/kb/249321

> http://support.microsoft.com/kb/223188/

>

>

> --

>

> Regards,

>

> Dave Patrick ....Please no email replies - reply in newsgroup.

> Microsoft Certified Professional

> Microsoft MVP [Windows]

> http://www.microsoft.com/protect

>

>

> "NoSpam Man" wrote:

>> Hi,

>>

>> I have added an external eSATA drive to my server which I wanted to

>> install vista onto. The idea was I could shut down w2003 server, plug in

>> the external eSATA drive, change the BIOS to put this external drive as

>> the first boot drive, and boot up vista. I would also be able to remove

>> this drive, boot up and go back into W2003 server.

>>

>> So I setup the bios as above, with the eSATA drive plugged in, booted up

>> installed Vista onto the external drive, and it works fine.

>>

>> Problem is that now there is a problem with the W2003 server.

>>

>> It boots with 'service failed to start.......) message, and goes to the

>> login screen, but when I log in to the server it logs me off and back to

>> the login screen. Even with the Administrator login, the same occurs, so

>> I am locked out. When I use RDC to login in, the login processes and

>> then the RDC is closed.

>>

>> I can access the server (\\server\\D$) and other services, however what

>> was the C$ seems to now be the F$. For some reason its changed my old C$

>> to F$ (the external eSATA is not plugged in)

>>

>> I can also access the event log on the server from another machine, and I

>> can see the following two error in the log.

>>

>> Any idea what I can do to resolve this????

>>

>> --

>> Windows cannot query for the list of Group Policy objects. Check the

>> event log for possible messages previously logged by the policy engine

>> that describes the reason for this.

>>

>> ---

>> Windows cannot access the file gpt.ini for GPO

>> CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=chelsea,DC=local.

>> The file must be present at the location

>> <\\chelsea.local\sysvol\chelsea.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>.

>> (Configuration information could not be read from the domain controller,

>> either because the machine is unavailable, or access has been denied. ).

>> Group Policy processing aborted.

>>

>>

>>

>>

>>

>

[Guest Pegasus \(MVP\)]

Re: Automaticcly logged off the moment I login in on the DC using any account

 

You could modify the permissions of this registry setting so that your

account is the only account that can modify it.

 

 

"NoSpam Man" <nospam@nospam.com> wrote in message

news:u7j1YbdIJHA.2156@TK2MSFTNGP05.phx.gbl...

> Hi...

>

> Thanks for your reply.

>

> Using a vista machine I start the regedit and connect to the network

> register for the server.

>

> I am able to connect find the setting and do as you suggest.

>

> I can close regedit, and reopen it, and see that the setting is now set to

> C:

>

> However when I reboot the server, it is somehow reset to be the F: and the

> C: is setting is gone.

>

> Any idea on what is happening ?

>

> Thanks

>

>

>

> "Pegasus (MVP)" <I.can@fly.com.oz> wrote in message

> news:OEf4whUIJHA.1160@TK2MSFTNGP04.phx.gbl...

>> HKLM is not a file; it is the H_Key_Local_Machine registry hive. That's

>> why I suggested you should open the server's registry. You do it with

>> regedit.exe.

>>

>> "NoSpam Man" <nospam@nospam.com> wrote in message

>> news:O$M6CMUIJHA.1160@TK2MSFTNGP04.phx.gbl...

>>> HI,

>>> Thanks for you answer..

>>>

>>> Where do I find the directory HKLM

>>>

>>> I can not see it under the \windows\system or system32

>>>

>>>

>>> "Pegasus (MVP)" <I.can@fly.com.oz> wrote in message

>>> news:%23HtmzzSIJHA.4280@TK2MSFTNGP04.phx.gbl...

>>>>

>>>> "NoSpam Man" <nospam@nospam.com> wrote in message

>>>> news:uJM6loRIJHA.4836@TK2MSFTNGP03.phx.gbl...

>>>>> Hi,

>>>>>

>>>>> I have added an external eSATA drive to my server which I wanted to

>>>>> install vista onto. The idea was I could shut down w2003 server, plug

>>>>> in the external eSATA drive, change the BIOS to put this external

>>>>> drive as the first boot drive, and boot up vista. I would also be able

>>>>> to remove this drive, boot up and go back into W2003 server.

>>>>>

>>>>> So I setup the bios as above, with the eSATA drive plugged in, booted

>>>>> up installed Vista onto the external drive, and it works fine.

>>>>>

>>>>> Problem is that now there is a problem with the W2003 server.

>>>>>

>>>>> It boots with 'service failed to start.......) message, and goes to

>>>>> the login screen, but when I log in to the server it logs me off and

>>>>> back to the login screen. Even with the Administrator login, the same

>>>>> occurs, so I am locked out. When I use RDC to login in, the login

>>>>> processes and then the RDC is closed.

>>>>>

>>>>> I can access the server (\\server\\D$) and other services, however

>>>>> what was the C$ seems to now be the F$. For some reason its changed my

>>>>> old C$ to F$ (the external eSATA is not plugged in)

>>>>>

>>>>> I can also access the event log on the server from another machine,

>>>>> and I can see the following two error in the log.

>>>>>

>>>>> Any idea what I can do to resolve this????

>>>>>

>>>>> --

>>>>> Windows cannot query for the list of Group Policy objects. Check the

>>>>> event log for possible messages previously logged by the policy engine

>>>>> that describes the reason for this.

>>>>>

>>>>> ---

>>>>> Windows cannot access the file gpt.ini for GPO

>>>>> CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=chelsea,DC=local.

>>>>> The file must be present at the location

>>>>> <\\chelsea.local\sysvol\chelsea.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>.

>>>>> (Configuration information could not be read from the domain

>>>>> controller, either because the machine is unavailable, or access has

>>>>> been denied. ). Group Policy processing aborted.

>>>>>

>>>>

>>>> This one is easily solved. Open the server's registry from a networked

>>>> machine, then do this:

>>>> 1. Navigate to HKLM\SYSTEM\MountedDevices

>>>> 2. Rename \DosDevices\F: to DosDevices\C:.

>>>> 3. Reboot the machine with shutdown.exe.

>>>> If there is already a DosDevices\C:, rename it to DosDevices\X:.

>>>>

>>>>

>>>

>>

>>

>

[Guest Dave Patrick]

Re: Automaticcly logged off the moment I login in on the DC using any account

 

Did you remove the external disk and whatever changes to cmos setup?

 

 

--

 

Regards,

 

Dave Patrick ....Please no email replies - reply in newsgroup.

Microsoft Certified Professional

Microsoft MVP [Windows]

http://www.microsoft.com/protect

 

 

"NoSpam Man" wrote:

> Hi

> Thanks for your reply.

>

> I followed these instructions, and the mounted device was wrong, so I

> renamed it.

>

> I rebooted the machine, but it put back the mounted device to be the wrong

> letter again somehow.

>

> I tried again, checked my permission, and reset the value. I was also able

> to restart regedit and could see that my edit to correct the mounted

> device was saved. Yet again when I rebooted it puts the C drive to be the

> G drive and the problem is still there.

>

> Is there something else that could be done to solve this?

>

> Thanks

[Guest NoSpam Man]

Re: Automaticcly logged off the moment I login in on the DC using any account

 

Yes did all that. CMOS shows no hard disk when its not attached

 

 

"Dave Patrick" <DSPatrick@nospam.gmail.com> wrote in message

news:%230eJCSjIJHA.696@TK2MSFTNGP02.phx.gbl...

> Did you remove the external disk and whatever changes to cmos setup?

>

>

> --

>

> Regards,

>

> Dave Patrick ....Please no email replies - reply in newsgroup.

> Microsoft Certified Professional

> Microsoft MVP [Windows]

> http://www.microsoft.com/protect

>

>

> "NoSpam Man" wrote:

>> Hi

>> Thanks for your reply.

>>

>> I followed these instructions, and the mounted device was wrong, so I

>> renamed it.

>>

>> I rebooted the machine, but it put back the mounted device to be the

>> wrong letter again somehow.

>>

>> I tried again, checked my permission, and reset the value. I was also

>> able to restart regedit and could see that my edit to correct the mounted

>> device was saved. Yet again when I rebooted it puts the C drive to be the

>> G drive and the problem is still there.

>>

>> Is there something else that could be done to solve this?

>>

>> Thanks

>

[Guest Dave Patrick]

Re: Automaticcly logged off the moment I login in on the DC using any account

 

Have you tried procedure five?

 

FDISK /MBR

 

 

--

 

Regards,

 

Dave Patrick ....Please no email replies - reply in newsgroup.

Microsoft Certified Professional

Microsoft MVP [Windows]

http://www.microsoft.com/protect

 

 

"NoSpam Man" wrote:

> Yes did all that. CMOS shows no hard disk when its not attached

[Guest NoSpam Man]

Re: Automaticcly logged off the moment I login in on the DC using any account

 

Another point of interest that may have something to do with this problem

is...

 

 

When I attached the eSATA drive, I moved that hdd to the top of the boot

priority list in the BIOS of the machine.

 

I rebooted, and would have expect the machine to have installed windows on

this drive (which it did fine), but no have changed anything on the other

drives.

 

It would seem for what ever reason this is not the case, as when I boot up I

get asked the question do I want to boot up Windows Vista or Previous

version of Windows.

 

This is asked even when the eSATA is not attached, and the internal 2003

disk is the top of the priority boot order in the BIOS.

 

When I look at the boot.ini file on the internal 2003 hdd, it has 'previous

version' on \partion(1)\

 

Would changing this to (0) help or just make a bigger mess?

 

Thanks for you help on this.

 

 

"NoSpam Man" <nospam@nospam.com> wrote in message

news:uURBtXfIJHA.2208@TK2MSFTNGP02.phx.gbl...

> Hi

> Thanks for your reply.

>

> I followed these instructions, and the mounted device was wrong, so I

> renamed it.

>

> I rebooted the machine, but it put back the mounted device to be the wrong

> letter again somehow.

>

> I tried again, checked my permission, and reset the value. I was also able

> to restart regedit and could see that my edit to correct the mounted

> device was saved. Yet again when I rebooted it puts the C drive to be the

> G drive and the problem is still there.

>

> Is there something else that could be done to solve this?

>

> Thanks

>

> "Dave Patrick" <DSPatrick@nospam.gmail.com> wrote in message

> news:e7qCh4WIJHA.1156@TK2MSFTNGP04.phx.gbl...

>> These articles may help.

>>

>> http://support.microsoft.com/kb/249321

>> http://support.microsoft.com/kb/223188/

>>

>>

>> --

>>

>> Regards,

>>

>> Dave Patrick ....Please no email replies - reply in newsgroup.

>> Microsoft Certified Professional

>> Microsoft MVP [Windows]

>> http://www.microsoft.com/protect

>>

>>

>> "NoSpam Man" wrote:

>>> Hi,

>>>

>>> I have added an external eSATA drive to my server which I wanted to

>>> install vista onto. The idea was I could shut down w2003 server, plug in

>>> the external eSATA drive, change the BIOS to put this external drive as

>>> the first boot drive, and boot up vista. I would also be able to remove

>>> this drive, boot up and go back into W2003 server.

>>>

>>> So I setup the bios as above, with the eSATA drive plugged in, booted up

>>> installed Vista onto the external drive, and it works fine.

>>>

>>> Problem is that now there is a problem with the W2003 server.

>>>

>>> It boots with 'service failed to start.......) message, and goes to the

>>> login screen, but when I log in to the server it logs me off and back to

>>> the login screen. Even with the Administrator login, the same occurs, so

>>> I am locked out. When I use RDC to login in, the login processes and

>>> then the RDC is closed.

>>>

>>> I can access the server (\\server\\D$) and other services, however what

>>> was the C$ seems to now be the F$. For some reason its changed my old C$

>>> to F$ (the external eSATA is not plugged in)

>>>

>>> I can also access the event log on the server from another machine, and

>>> I can see the following two error in the log.

>>>

>>> Any idea what I can do to resolve this????

>>>

>>> --

>>> Windows cannot query for the list of Group Policy objects. Check the

>>> event log for possible messages previously logged by the policy engine

>>> that describes the reason for this.

>>>

>>> ---

>>> Windows cannot access the file gpt.ini for GPO

>>> CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=chelsea,DC=local.

>>> The file must be present at the location

>>> <\\chelsea.local\sysvol\chelsea.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>.

>>> (Configuration information could not be read from the domain controller,

>>> either because the machine is unavailable, or access has been denied. ).

>>> Group Policy processing aborted.

>>>

>>>

>>>

>>>

>>>

>>

>

[Guest Dave Patrick]

Re: Automaticcly logged off the moment I login in on the DC using any account

 

Yes, that makes a big difference. Sounds like the Vista boot environment was

installed on this disk. Probably the first primary active partition. You

might try fixmbr and fixboot from the Windows Server 2003 recovery console.

 

 

 

--

 

Regards,

 

Dave Patrick ....Please no email replies - reply in newsgroup.

Microsoft Certified Professional

Microsoft MVP [Windows]

http://www.microsoft.com/protect

 

 

"NoSpam Man" wrote:

> Another point of interest that may have something to do with this problem

> is...

>

>

> When I attached the eSATA drive, I moved that hdd to the top of the boot

> priority list in the BIOS of the machine.

>

> I rebooted, and would have expect the machine to have installed windows on

> this drive (which it did fine), but no have changed anything on the other

> drives.

>

> It would seem for what ever reason this is not the case, as when I boot up

> I get asked the question do I want to boot up Windows Vista or Previous

> version of Windows.

>

> This is asked even when the eSATA is not attached, and the internal 2003

> disk is the top of the priority boot order in the BIOS.

>

> When I look at the boot.ini file on the internal 2003 hdd, it has

> 'previous version' on \partion(1)\

>

> Would changing this to (0) help or just make a bigger mess?

>

> Thanks for you help on this.

>

>

> "NoSpam Man" <nospam@nospam.com> wrote in message

> news:uURBtXfIJHA.2208@TK2MSFTNGP02.phx.gbl...

>> Hi

>> Thanks for your reply.

>>

>> I followed these instructions, and the mounted device was wrong, so I

>> renamed it.

>>

>> I rebooted the machine, but it put back the mounted device to be the

>> wrong letter again somehow.

>>

>> I tried again, checked my permission, and reset the value. I was also

>> able to restart regedit and could see that my edit to correct the mounted

>> device was saved. Yet again when I rebooted it puts the C drive to be the

>> G drive and the problem is still there.

>>

>> Is there something else that could be done to solve this?

>>

>> Thanks

[Guest NoSpam Man]

Re: Automaticcly logged off the moment I login in on the DC using any account

 

Hi,

 

Still having the problem...

 

What I have done now is to remove all the drives except the one with my

windows 2003 server on it from the machine (1 internal hdd, 1 ext eSATA

drive)

 

With just the one internal hdd, It is happy to boot up and log in fine. The

C:\ is as it should be and all is well. Checked the mounted devices in the

registry and its perfect.

 

However ...

 

Even in this configuration when I boot into windows recovery mode it asks

which installation of windows do I want to work with, and it says

f:\windows... It should say C:\windows

 

 

and

 

Now if I put back my other internal drive it has the problem where what

should be the c drive is now the f drive. there is no c drive at all. (I

determined this by connection from another machine to the server \\server\C$

d$ e$ etc... what should be the c$ is actually the f$)

 

Whilst the machine was booted with just the one drive, and the machine

worked fine, I did did 'fixmbr' and 'fixboot'. It still reboots with the

problem

 

I am at a total loss....

 

 

 

 

"Dave Patrick" <DSPatrick@nospam.gmail.com> wrote in message

news:OopOgTkIJHA.1308@TK2MSFTNGP02.phx.gbl...

> Yes, that makes a big difference. Sounds like the Vista boot environment

> was installed on this disk. Probably the first primary active partition.

> You might try fixmbr and fixboot from the Windows Server 2003 recovery

> console.

>

>

>

> --

>

> Regards,

>

> Dave Patrick ....Please no email replies - reply in newsgroup.

> Microsoft Certified Professional

> Microsoft MVP [Windows]

> http://www.microsoft.com/protect

>

>

> "NoSpam Man" wrote:

>> Another point of interest that may have something to do with this problem

>> is...

>>

>>

>> When I attached the eSATA drive, I moved that hdd to the top of the boot

>> priority list in the BIOS of the machine.

>>

>> I rebooted, and would have expect the machine to have installed windows

>> on this drive (which it did fine), but no have changed anything on the

>> other drives.

>>

>> It would seem for what ever reason this is not the case, as when I boot

>> up I get asked the question do I want to boot up Windows Vista or

>> Previous version of Windows.

>>

>> This is asked even when the eSATA is not attached, and the internal 2003

>> disk is the top of the priority boot order in the BIOS.

>>

>> When I look at the boot.ini file on the internal 2003 hdd, it has

>> 'previous version' on \partion(1)\

>>

>> Would changing this to (0) help or just make a bigger mess?

>>

>> Thanks for you help on this.

>>

>>

>> "NoSpam Man" <nospam@nospam.com> wrote in message

>> news:uURBtXfIJHA.2208@TK2MSFTNGP02.phx.gbl...

>>> Hi

>>> Thanks for your reply.

>>>

>>> I followed these instructions, and the mounted device was wrong, so I

>>> renamed it.

>>>

>>> I rebooted the machine, but it put back the mounted device to be the

>>> wrong letter again somehow.

>>>

>>> I tried again, checked my permission, and reset the value. I was also

>>> able to restart regedit and could see that my edit to correct the

>>> mounted device was saved. Yet again when I rebooted it puts the C drive

>>> to be the G drive and the problem is still there.

>>>

>>> Is there something else that could be done to solve this?

>>>

>>> Thanks

>