cluberti

http://www.windowsnetworking.com/kbase/Win...countsinAD.html

Download Process Explorer, and use the "Find" menu. Type the name of the .avi file, and you'll see what process or processes have a handle to the file.

The moral of the story is to use UAC, rather than fight it, and this isn't a problem if UAC is enabled. OT, but relevant: It's amazing how Windows gets flogged for lax security (which I don't believe is the case anymore with XP SP2 and 2K3 SP1), but when restrictive security measures (similar to everyone's darling Linux) are implemented, people rush to disable those features because they're inconvenient or somewhat obtrusive. Sorry to rant, but I saw UAC in a post and got all soap-boxy .

I believe you're missing the brightness and screen orientation sections. At least that's the way it was on builds previous to RTM - I'll have to put this on my laptop at some point and check if that's still the case, or if those two are gone for good. I also believe these are display and monitor driver specific sections, requiring compatibile drivers to display these sections.

How about this - create a local non-admin, non-domain user on the machine and attempt to change network settings. Does it work? Does it work if you change a domain user's profile to local rather than roaming? If you remove and re-add the machine to the domain, does it work then?

Key: HKCU\Software\Microsoft\Windows NT\CurrentVersion\Setup\Welcome Value: srvwiz Type: REG_DWORD Data: 0 = disable, 1 = display wizard

RTM for all versions is 6000.16386.061101-2205. Dates are 11/2/06 for all versions. Remember, Vista is built as one product build for all SKUs, and the product key or version chosen determines what bits are installed from that one large build.

Can the movie play in safe mode?

Not sure about the posted application, but for your situation it sounds like W2K3 would suit you better in the long run. You can get around fast user switching, and any good free antivirus package is sufficient if that's what you require. Once you start needing to do server work and testing, using a client OS makes less sense if using a server OS isn't a big inconvenience.

A simple way to look would be to run filemon on both machines, doing the same operation, and compare logs.

If you just moved files, but didn't copy using an imaging program or sector copy program, the mft on the disk is all screwed up now and will give you this error until you do a repair installation.

Memory is good to check, but a BIOS upgrade isn't a bad idea either. NT kernel-based OSes will tax the hardware and BIOS much heavier than 9x-based versions of Windows, and a BIOS upgrade can sometimes smooth out issues like this. Since introducing the NT kernel seems to be related to your problems, a BIOS upgrade (to make sure you're running the latest version for your motherboard) is always a good thing when going from 9x to 2000 or XP.

WinPE or BartPE are the way to go - the Windows installer doesn't contain this functionality natively.

It's worth noting that almost all group policy settings are enforced via the registry, and you can easily see (most times) what you're looking for by editing the .adm and finding the entry you are configuring. This will tell you what registry key and value are being modified, and what the appropriate values are.

If you've got a Windows 2000 or 2003 server machine, RIS would be easier. If you are doing straight network installs from a network share, that's probably the best way. Note that there are ways to do RIS via a Linux server, although I've not tried it: http://oss.netfarm.it/guides/pxe.php

You'll likely have to boot to the w2k recovery console and run fixboot and fixmbr, and maybe even perform a repair install once you can see the volume. Otherwise, you'll probably want to image that partition (sector copy to save the data on it) and reinstall.

Check out KB's 279151 and 822842 for a hint of what's happening. Basically, the BIOS will reserve RAM for shadowing or buffer (for things like hot-add memory, PCI-X bus, video shadowing, etc), and when we boot up, we do check to see if the BIOS has reserved memory. If you run msinfo32, you'll probably see the correct amount of RAM installed in your system displayed, as this amount is displayed as the result of WMI calls to the BIOS for the physical amount of installed RAM (regardless of reservation) - however, the amount on the general tab shows you how much Windows can and is actually using. If you've got Windows Server 2000 Advanced edition or Server 2003 Enterprise, you can add the /3GB switch and possibly see all of the memory in the general tab, but this is not recommended as attempting to use memory reserved by the BIOS results in system instability.

Ah yes - starforce + Daemon Tools = lots of bugchecks. If you've got both, get rid of one or the other .

There's a reason that no one will explain that to you, but I can't go into more detail. If you have an MS support agreement, ask your TAM.

A TAP customer would've been running 5840 (and higher) builds, and would likely already know how RTM runs (about the same as the 58xx builds, minus some bugs). However, OEM and MSDN have been available since Monday, and that makes this a possible legit question. And you don't need a key to get the 30 day trial, besides.

I love the EU. Hand over your IP if you want to business here...

Follow these steps to enable complete memory dumps (this assumes a PS/2 keyboard is attached): 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"; this will open the "System Properties" window. Go to the "Advanced" tab and click "Performance Options". 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, click on the "Advanced" tab, then click "Startup and Recovery". 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 the issue is occurring, hold down the RIGHT CTRL key and press the SCROLL LOCK key twice to cause the server to bugcheck and create a memory.dmp file, by default in the root of the Windows directory. Once the box reboots and disk activity dies down, you should have a dump we can analyze.

Very interesting - if you connect to it remotely via RDP, can you log into it from another machine via an RDP connection?

Vista uses WDS for network deployment, not RIS: http://www.microsoft.com/technet/WindowsVi...80fc215130.mspx

ALL bits are on one DVD. The pidgen on the disk will allow it to determine what bits to install, and all versions (even VL) will require activating the key used to install.