cluberti

First, I've PM'ed you an FTP location to upload the .dmp file to, and I'll analyze it. Second, if you choose to boot into safe mode, does the startup and shutdown issue of slowness persist?

You've created a new OU, placed this one and only machine in that new OU, linked policies to this OU one at a time, and you still don't know which one is causing this?

Generally, no. There are some hacks, but I would not recommend it. Look into roaming profiles and folder redirection.

If you go into the Terminal Services Configuration on the server and open the properties of the RDP connection object, you should be able to see if any logout settings are configured on the "Sessions" tab.

Does that machine have a PS/2 keyboard? If so, boot up and then do the following: 1. Create or set the following registry value: Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters Value: CrashOnCtrlScroll Type: REG_DWORD Data: 1 2. Right-Click on the "My Computer" icon on the desktop and select "Properties", then click the "Advanced system settings" option in the left-hand pane of the window. On the "Advanced" tab, click "Settings" under the "Performance:" header. Click the "Advanced" tab, then click "Change" under "Virtual Memory". Set the pagefile to be located on the partition where the OS is installed, and set it to be equal to Physical RAM + 50 MB. 3. Also in the "System Properties" window on the "Advanced" tab, click the "Settings" buttun under the "Startup and Recovery" header. Make sure "Complete Memory Dump" is selected (see 3a if this is not in the list). You can change the location of the memory dump file to a different local partition if you do not have enough room on the partition where the OS is installed. 3a. If the "Complete Memory Dump" option in step 3 is not available, you will need to manually set this registry value: Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl Value: CrashDumpEnabled Type: REG_DWORD Value: 1 4. You will need to reboot for these changes to take effect. 5. The next time that you boot up, and the system appears to be hanging, hold down the RIGHT CTRL key and press the SCROLL LOCK key twice to cause the machine to bugcheck and create a memory dump. After the box comes back up, you'll find the resulting memory dump file in %systemroot%\memory.dmp. This file can be analyzed to determine what was hanging during boot.

I've seen this happen quite a few times on Win2K after installing IE or shell updates to IE 5.x and IE 6.x versions, and I've never seen anything work other than rolling back the updates and crossing your fingers (it does work sometimes, if you haven't messed with the system too much since the errors started) or doing a repair install to replace the files and registry information.

Remember to search the web AND groups when doing a Google search, because Google is your friend: http://groups.google.com/group/microsoft.p...51bfbba21d7e298

I understand it's working other than WinPE, but I would still like to see a trace of the failure. It could be the network driver PE is using too, but that's hard to say without a trace and seeing the behavior.

Riprep images will work, but they're HAL-specific (just like sysprep) and they can have some other issues when pulled down from the RIS server. I don't have anything specific, but ping me offline for more data in PM.

If you have a partner in your area (or close), you may wish to give them a call or drop them an email to see if you can get a list of contacts for MCTs that they use. I've found that works for me, at least.

Terminal services needs to be activated due to the nature of the product (providing a virtual desktop to more than one or two users at a time, virtualizing application registries, etc). It requires TS licenses for every user, or every device, that will connect to the TS. This is above and beyond the licensing activation for the Windows Server 2003 OS license.

I believe Microsoft keeps track of MCTs in certain areas... http://directory.microsoft.com/mprd/Search...ageDropDown=173

Well, welcome! Hopefully you'll find that the forums here are quite civil, and quite helpful to boot . Glad to have you 'round.

Well, if you weren't such a jerk... oh wait, I see... Always a good reminder to keep it civil and above-board.

Have you taken a network trace from the DHCP server, or from a switch or hub between the client and WDS server, to see the actual DORA process and the error over the wire? Sometimes what the client reports as an error is not the real error you'd see in a network trace, especially if DHCP denied the client an IP address...

I hate to ask something obvious, but have you tried running these hotfixes with the associated switches in a VM with the clean OS loaded? Since most VM applications are free, it'd be worth trying to make sure it isn't giving you the error because the switches really are incorrect .

Well, considering that unchecking the Windows Media Player option doesn't actually uninstall it at all on XP (it hides all icons and clears file associations, but the binaries are all still on disk and registered in the registry), I'm not surprised you aren't given the option on Server 2003. We won't go into the discussion of why a server OS needs a media player (even TS you'd never want to stream or view media over RDP), but anyway...

I'd say your best bet is finding a version of the driver that doesn't load in IE7, since there's no conceivable reason I can think of for a system driver to be loading inside of IE, as the shell handles mouse component data, not IE. Oh well, live and learn.

Just for the edification of those who may not know and search for this, here's the KB on how to do it: 319878: How to make Outlook Web Access the default Web site http://support.microsoft.com/default.aspx?...kb;EN-US;319878

It would be interesting to get a network trace from one of the machines after it's booted (leave the network cable out until you've booted and started the network trace on the NIC) to watch the DORA - see which DHCP server was responding to the initial discover, and whether or not that was the correct DHCP server (probably not!) .

Not necessarily - risetup will only copy the relevant files from i386 to the RIS server. You'll have to go into the image folder it creates and re-modify it (and the answer file in \<imagename>\i386\templates) to get things working as your CD does. Once you've done it on a CD install, it's pretty easy to look at a RIS install and go "oh, so I put these files and scripts here, and modify the answer file to look somewhat like the CD winnt.sif, and I'm good to go". Basically like that .

That's because the information about the RAID is stored on the disk (and the registry of the host machine, but it's stored on the disk too). XP and 2003 read and write the same volume information regarding basic disks, and should have little trouble reading each others' RAID volumes.

Are you getting "Low memory" warnings, or "Low Disk Space" warnings, specifically? They're different...

Does this happen in safe mode?

It won't be, due to things like TCP overhead. In fact, you're lucky if you get 70% of the rated speed of your network.