demote the server

[George Hester MVP - IIS]

Who has ever done this and lived to tell about? But of course if you didn't
live to tell about it, then I cannot expect an answer now can I? It all
went smoothly without a hitch. After the reboot the prettiest empty desktop
you could imagine. IE no longer worked. Add Windows Components didnt'
work. I did get a populated desktop after shaking some sense into the
system and did get an IE window to appear by Start | Run |
http://www.microsoft.com | OK. But it never connected. I happened to have
Netscape 4.8 installed and that worked just fine. So connection was
working.

If anyone has any ideas how to fix this installation I'm open to any and all
ideas. Otherwise toast anyone?

It was Windows 2000 SP4.

 

[Lanwench [MVP - Exchange]]

Who has ever done this and lived to tell about?

I have.

But of course if you
didn't live to tell about it, then I cannot expect an answer now can
I? It all went smoothly without a hitch. After the reboot the
prettiest empty desktop you could imagine. IE no longer worked. Add
Windows Components didnt' work. I did get a populated desktop after
shaking some sense into the system and did get an IE window to appear
by Start | Run | http://www.microsoft.com | OK. But it never
connected. I happened to have Netscape 4.8 installed and that worked
just fine. So connection was working.

Who were you logging in as, and did that account exist and work properly
before demoting the server?

If anyone has any ideas how to fix this installation I'm open to any
and all ideas. Otherwise toast anyone?

Event log errors?
If we're toasting, I'll take a gin and tonic with extra lime, please.

It was Windows 2000 SP4.

I'd presume it still is.

 

[George Hester]

No not anymore. It's an imposter now. User was Administrator when demoted
user was Administrator when logged back in after start. Of course it REALLY
was Administrator.MachineName but let's let that go for now.

No the account did NOT exist before demoting. It's not possible to make an
Administrator.MachineName account anyway. When the Server becomes
standalone an Administrator account is made in the demotion process.

Event viewer? That probably doesn't work anymore either. But I can check.
Toast as in burned bread. That toast.

 

[Lanwench [MVP - Exchange]]

No not anymore. It's an imposter now. User was Administrator when
demoted user was Administrator when logged back in after start. Of
course it REALLY was Administrator.MachineName but let's let that go
for now.

That's just the profile name. Not relevant to the user account really. So
you were using the domain admin account - is there another DC for this
domain, and can you log in there successfully?

No the account did NOT exist before demoting. It's not possible to
make an Administrator.MachineName account anyway.

Well, there's no local user database on a DC...maybe I wasn't very clear.

When the Server
becomes standalone an Administrator account is made in the demotion
process.

Event viewer? That probably doesn't work anymore either. But I can
check. Toast as in burned bread. That toast.

Check...and post back.

 

[George Hester]

It's a standalone server now. In name only. Not a member server. I'll see
what the EV says.

 

[George Hester]

OK Lanwench here we go:

In System Log:

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 3095
Date: 11/10/2004
Time: 11:35:16 PM
User: N/A
Computer: MyComputer
Description:
This Windows NT computer is configured as a member of a workgroup, not as a member of a domain. The Netlogon service does not need to run in this configuration.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 11/10/2004
Time: 11:35:16 PM
User: N/A
Computer: MyComputer
Description:
The Net Logon service terminated with service-specific error 3095.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 11/10/2004
Time: 11:35:30 PM
User: N/A
Computer: MyComputer
Description:
The Fax Service service depends on the Net Logon service which failed to start because of the following error:
The service has returned a service-specific error code.

Event Type: Error
Event Source: Server
Event Category: None
Event ID: 2511
Date: 11/10/2004
Time: 11:35:35 PM
User: N/A
Computer: MyComputer
Description:
The server service was unable to recreate the share SYSVOL because the directory C:\WINNT\sysvol\sysvol no longer exists.

Event Type: Error
Event Source: Server
Event Category: None
Event ID: 2511
Date: 11/10/2004
Time: 11:35:35 PM
User: N/A
Computer: MyComputer
Description:
The server service was unable to recreate the share NETLOGON because the directory C:\WINNT\sysvol\sysvol\MyComputerloli.com\SCRIPTS no longer exists.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7013
Date: 11/10/2004
Time: 11:35:35 PM
User: N/A
Computer: MyComputer
Description:
Logon attempt with current password failed with the following error:
Logon failure: the user has not been granted the requested logon type at this computer.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 11/10/2004
Time: 11:35:35 PM
User: N/A
Computer: MyComputer
Description:
The MSSQLSERVER service failed to start due to the following error:
The service did not start due to a logon failure.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 11/10/2004
Time: 11:35:51 PM
User: N/A
Computer: MyComputer
Description:
The SQLSERVERAGENT service depends on the MSSQLSERVER service which failed to start because of the following error:
The service did not start due to a logon failure.

Event Type: Error
Event Source: DhcpServer
Event Category: None
Event ID: 1041
Date: 11/10/2004
Time: 11:37:28 PM
User: N/A
Computer: MyComputer
Description:
The DHCP service is not servicing any clients because none of the active network interfaces have statically configured IP addresses, or there are no active interfaces.
Data:
0000: 00 00 00 00 ....

In Application Log:

Event Type: Error
Event Source: MSMQ
Event Category: Kernel
Event ID: 2021
Date: 11/10/2004
Time: 11:36:18 PM
User: N/A
Computer: MyComputer
Description:
Unable to obtain computer information from Active Directory.

Event Type: Error
Event Source: LoadPerf
Event Category: None
Event ID: 3011
Date: 11/10/2004
Time: 11:36:21 PM
User: N/A
Computer: MyComputer
Description:
Unloading the performance counter strings for FileReplicaSet failed. The Error code is DWORD 0 of the Record Data.
Data:
0000: 02 00 00 00 ....

Event Type: Error
Event Source: LoadPerf
Event Category: None
Event ID: 3009
Date: 11/10/2004
Time: 11:36:22 PM
User: N/A
Computer: MyComputer
Description:
Installing the performance counter strings for FileReplicaSet failed. The Error code is DWORD 0 of the Record Data.
Data:
0000: b7 00 00 00 ·...

Event Type: Error
Event Source: LoadPerf
Event Category: None
Event ID: 3011
Date: 11/10/2004
Time: 11:36:23 PM
User: N/A
Computer: MyComputer
Description:
Unloading the performance counter strings for FileReplicaConn failed. The Error code is DWORD 0 of the Record Data.
Data:
0000: 02 00 00 00 ....

Event Type: Error
Event Source: LoadPerf
Event Category: None
Event ID: 3009
Date: 11/10/2004
Time: 11:36:25 PM
User: N/A
Computer: MyComputer
Description:
Installing the performance counter strings for FileReplicaConn failed. The Error code is DWORD 0 of the Record Data.
Data:
0000: b7 00 00 00 ·...

Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 46
Date: 11/10/2004
Time: 11:36:26 PM
User: N/A
Computer: MyComputer
Description:
WMI ADAP was unable to retrieve data from the PerfLib localization subkey: , error code: 0x2

Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 60
Date: 11/10/2004
Time: 11:36:28 PM
User: N/A
Computer: MyComputer
Description:
WMI ADAP was unable to process the performance libraries: 0x80041001

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1004
Date: 11/10/2004
Time: 11:40:53 PM
User: N/A
Computer: MyComputer
Description:
Detection of product '{90110409-6000-11D3-8CFE-0150048383C9}', feature 'OfficeUserData', component '{4A31E933-6F67-11D2-AAA2-00A0C90F57B0}' failed. The resource 'HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\MS Access Database\' does not exist.

In the rest:

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13566
Date: 11/7/2004
Time: 12:27:28 AM
User: N/A
Computer: MyComputer
Description:
File Replication Service is scanning the data in the system volume. Computer MyComputer cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.

To check for the SYSVOL share, at the command prompt, type:
net share

When File Replication Service completes the scanning process, the SYSVOL share will appear.

The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume.

Not a pretty picture. The Installer is broken. Most everything else is broken as well. The demotion demolished. Maybe that's the way Microsoft should advertise this. Demote ack that's a good one more like Demolish if you ask me.