I have Server 2003R2 installed on an HP DL360 G5 which has been in operation for a few years. About a year ago, the boot time went from normal (a few minutes) to slow (around 30 minutes), and in the last few months to extremely slow (over 60 minutes) Immediately after reboot, I am able to Ctrl-Alt-Del, and then log in, and it displays "Loading your personal settings..." for roughly an hour. When I look at Event viewer, nothing stands out. I have tried to boot in safe mode with no difference. I have tried creating and logging in as a different user with no change. I am NOT using this server as a DNS Domain and it is just assigned to a workgroup. Does anyone have any ideas?

Try to enable verbose logging: http://support.microsoft.com/kb/325376/en-us Marc

Hello, Please start like that: Disable all security softwares that you haveUpdate all possible driversUninstall all unused programsRun msconfig and disable all startup items / services except Microsoft ones Once done, reboot your server and check results. Please also check event logs in event viewer. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer

I have tried all of the above, and already had verbose logging turned on, the only warnings in the event viewer are as follows: Event Type: Warning Event Source: DNS Event Category: None Event ID: 414 Date: 2/17/2012 Time: 1:50:04 PM User: N/A Computer: IONSRVR Description: The DNS server machine currently has no DNS domain name. Its DNS name is a single label hostname with no domain (example: "host" rather than "host.microsoft.com"). You might have forgotten to configure a primary DNS domain for the server computer. For more information, see either "DNS server log reference" or "To configure the primary DNS suffix for a client computer" in the online Help. While the DNS server has only a single label name, all zones created will have default records (SOA and NS) created using only this single label name for the server's hostname. This can lead to incorrect and failed referrals when clients and other DNS servers use these records to locate this server by name. To correct this problem: 1) open Control Panel 2) open System applet 3) select Computer Name tab 4) click the "Change" button and join the computer to a domain or workgroup; this name will be used as your DNS domain name 5) reboot to initialize with new domain name After reboot, the DNS server will attempt to fix up default records, substituting new DNS name of this server, for old single label name. However, you should review to make sure zone's SOA and NS records now properly use correct domain name of this server. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Warning Event Source: Foundation Agents Event Category: Alerter Event ID: 770 Date: 2/17/2012 Time: 1:56:35 PM User: N/A Computer: IONSRVR Description: The Host Remote Alerter detected an error while attempting to retrieve data from key = CompaqHost\OsPerf\Component\Processor in the registry. The data contains the error code. Data: 0000: ea 00 00 00 ... I have it down to running only the necessary programs.

have you install SP1 of windows server 2008 r2?

The initial install was Server 2003 R2 SP1, we have since installed SP2 Here are the userenv.log file entries from the time I logged in as Administrator (13:03) up to the time the system actually started coming up (12:56) USERENV(3b8.460) 13:00:26:031 LibMain: Process Name: C:\WINDOWS\system32\spoolsv.exe USERENV(32c.370) 13:03:00:203 LoadUserProfile: Yes, we can impersonate the user. Running as self USERENV(32c.370) 13:03:00:203 ========================================================= USERENV(32c.370) 13:03:00:203 LoadUserProfile: Entering, hToken = <0x4f8>, lpProfileInfo = 0x17eefdc USERENV(32c.370) 13:03:00:203 LoadUserProfile: lpProfileInfo->dwFlags = <0x1> USERENV(32c.370) 13:03:00:203 LoadUserProfile: lpProfileInfo->lpUserName = <Administrator> USERENV(32c.370) 13:03:00:203 LoadUserProfile: lpProfileInfo->lpProfilePath = <> USERENV(32c.370) 13:03:00:203 LoadUserProfile: NULL default profile path USERENV(32c.370) 13:03:00:203 LoadUserProfile: NULL server name USERENV(32c.370) 13:03:00:203 LoadUserProfile: no thread token found, impersonating self. USERENV(32c.370) 13:03:00:203 GetInterface: Returning rpc binding handle USERENV(188.458) 13:03:00:203 IProfileSecurityCallBack: client authenticated. USERENV(188.458) 13:03:00:203 DropClientContext: Got client token 0000069C, sid = S-1-5-18 USERENV(188.458) 13:03:00:203 MIDL_user_allocate enter USERENV(188.458) 13:03:00:203 DropClientContext: load profile object successfully made USERENV(188.458) 13:03:00:203 DropClientContext: Returning 0 USERENV(32c.370) 13:03:00:203 LoadUserProfile: Calling DropClientToken (as self) succeeded USERENV(188.2b4) 13:03:00:203 IProfileSecurityCallBack: client authenticated. USERENV(188.2b4) 13:03:00:203 In LoadUserProfileP USERENV(188.2b4) 13:03:00:203 LoadUserProfile: Running as client, sid = S-1-5-18 USERENV(188.2b4) 13:03:00:203 ========================================================= USERENV(188.2b4) 13:03:00:203 LoadUserProfile: Entering, hToken = <0x7b8>, lpProfileInfo = 0xb91aa8 USERENV(188.2b4) 13:03:00:203 LoadUserProfile: lpProfileInfo->dwFlags = <0x1> USERENV(188.2b4) 13:03:00:203 LoadUserProfile: lpProfileInfo->lpUserName = <Administrator> USERENV(188.2b4) 13:03:00:203 LoadUserProfile: lpProfileInfo->lpProfilePath = <> USERENV(188.2b4) 13:03:00:203 LoadUserProfile: NULL default profile path USERENV(188.2b4) 13:03:00:203 LoadUserProfile: NULL server name USERENV(188.2b4) 13:03:00:203 LoadUserProfile: User sid: S-1-5-21-1939536379-135520416-2953878254-500 USERENV(188.2b4) 13:03:00:203 CSyncManager::EnterLock <S-1-5-21-1939536379-135520416-2953878254-500> USERENV(188.2b4) 13:03:00:203 CSyncManager::EnterLock: Found existing entry USERENV(188.18c) 13:03:32:843 LoadUserProfile: Yes, we can impersonate the user. Running as self USERENV(188.18c) 13:03:32:843 ========================================================= USERENV(188.18c) 13:03:32:843 LoadUserProfile: Entering, hToken = <0x7cc>, lpProfileInfo = 0x6e5d8 USERENV(188.18c) 13:03:32:843 LoadUserProfile: lpProfileInfo->dwFlags = <0x0> USERENV(188.18c) 13:03:32:843 LoadUserProfile: lpProfileInfo->lpUserName = <Administrator> USERENV(188.18c) 13:03:32:843 LoadUserProfile: NULL central profile path USERENV(188.18c) 13:03:32:843 LoadUserProfile: NULL default profile path USERENV(188.18c) 13:03:32:843 LoadUserProfile: NULL server name USERENV(188.18c) 13:03:32:843 LoadUserProfile: In console winlogon process USERENV(188.18c) 13:03:32:843 In LoadUserProfileP USERENV(188.18c) 13:03:32:843 ========================================================= USERENV(188.18c) 13:03:32:843 LoadUserProfile: Entering, hToken = <0x7cc>, lpProfileInfo = 0x6e5d8 USERENV(188.18c) 13:03:32:843 LoadUserProfile: lpProfileInfo->dwFlags = <0x0> USERENV(188.18c) 13:03:32:843 LoadUserProfile: lpProfileInfo->lpUserName = <Administrator> USERENV(188.18c) 13:03:32:843 LoadUserProfile: NULL central profile path USERENV(188.18c) 13:03:32:843 LoadUserProfile: NULL default profile path USERENV(188.18c) 13:03:32:843 LoadUserProfile: NULL server name USERENV(188.18c) 13:03:32:843 LoadUserProfile: User sid: S-1-5-21-1939536379-135520416-2953878254-500 USERENV(188.18c) 13:03:32:843 CSyncManager::EnterLock <S-1-5-21-1939536379-135520416-2953878254-500> USERENV(188.18c) 13:03:32:843 CSyncManager::EnterLock: Found existing entry USERENV(188.1a4) 13:56:05:796 MyRegLoadKey: Returning 00000000 USERENV(188.1a4) 13:56:05:812 GetUserDNSDomainName: Computer is running standalone. No DNS domain name available. USERENV(188.1a4) 13:56:05:828 MyRegLoadKeyEx: Loading key <S-1-5-21-1939536379-135520416-2953878254-500_Classes> USERENV(188.1a4) 13:56:05:859 MyRegLoadKeyEx: Successfully loaded <S-1-5-21-1939536379-135520416-2953878254-500_Classes> USERENV(188.1a4) 13:56:05:859 CreateClassHive: existing user classes hive found USERENV(188.1a4) 13:56:05:859 RestoreUserProfile: About to Leave. Final Information follows: USERENV(188.1a4) 13:56:05:859 Profile was successfully loaded. USERENV(188.1a4) 13:56:05:859 lpProfile->lpRoamingProfile = <> USERENV(188.1a4) 13:56:05:859 lpProfile->lpLocalProfile = <C:\Documents and Settings\Administrator>

Provided you have not done anything to the server, you may want to do a chkdsk on the OS volume. I have seen disks starting to go bad that have caused the exact problem you are describing. I would do an analyze first prior to doing actual fixes (sometimes, the fix can make issues worse). If the analyze phase reveals errors, do a full backup and then do a chksks to fix errors. Get ready for the pain.

Provided you have not done anything to the server, you may want to do a chkdsk on the OS volume. I have seen disks starting to go bad that have caused the exact problem you are describing. I would do an analyze first prior to doing actual fixes (sometimes, the fix can make issues worse). If the analyze phase reveals errors, do a full backup and then do a chksks to fix errors. Get ready for the pain.