allen2

It is most likely to reproduce the regmultisz key positioning after the registry is created. As for the max size, it may differ between 2000 or XP but the max theorical size should be something about 100MB divided by two for windows 2000 as i remember increasing the max size of the registry size on windows 2000 and making it crash using a value too big. Edit: found a link that might help it to be clearer:http://support.microsoft.com/kb/124594

For vmware virtual machines, you need an lsi driver(symmpi.sys) which is already in windows 2003 x64 CD.

I would also check the drive with the western digital tools.

While i agree with Jaclaz, i understand why you asked when you read the VISTA EULA. The paragraph 8 say: So in a way using Vlite may enter in the "work around any technical limitations in the software;" category as vista installer doesn't allow to remove some components but i am pretty sure nowhere in this world you would be sued for "this" (you're already sacrificing too much using Vista as Os).

Microsoft provide OEM disc/iso to the OEM and never to end users and sometimes manufacturers put it in the package you get with the computer along with the recoveryCD. Finding an OEM disc might not be that trivial as like all OEM disc is protected: For example an HP windows OEM disc won't work on a DELL (except in some rare cases) as it was designed like this even if you remove the HP drivers/customization and add the DELL's ones.

1 - Nlite was and is still the best tool for this. 2 - There are a lot of method and one of them is almost the same than the one used for win7: install a winpe on this partition and when triggered, the restore operation will overwrite the target partition with a wim containing XP partition. 3 - Yes there is a list security related updates provided by -X- but it doesn't contain all existing updates like dotnet related or hotfixes by request provided by Microsoft. 4 - The reg entry initialkeyboardindicator should help you but remember that there is more than one in your case and you'll have to set all values to 0 to fix the numlock problem. 5 - Microsoft can't provide for download OEM version but they provide retail version on your msdn/open account. You might ask your manufacturer if you 're downgrading from windows 7 as sometimes they are providing this service for free. But from what you said, if the laptop had XP home OEM, then you can't ever find a legal XP PRO OEM to replace it.

If you set the 2008 DC in active directory site and services in another subnet by putting it in another site and setting this site to only allow authentication of client of a subnet you don't use for production or don't use at all then no client should be able to use the 2008 DC.

I would do the dcpromo on Windows 2008 R2 and set it as a DC without any roles and not GC just add dns server integration or do it manually (before if done manually) and create a dedicated site for the 2008 DC disallow user authentication. Then i would check if everything is still working properly for users and check if AD replications are working (should take one hour). Then check the policies on the 2008 DC and compare them with the windows 2003 DC as there might be a gap as policies models aren't stored in sysvol anymore. Next step would be checking if the 2008 DC allow clients to logon as usual (still using active directory sites and services and use a small subnet the test clients). Then set it as GC and then transfer roles with ntdsutil (of course after each step check if there are side effects). The usual problems are the policies which you might need to recreate/reset entirely on the windows 2008R2 depending on the settings who were on the windows 2003 DC as compatibility isn't always there (and that was most like the problem you already encountered).

Most likely when your first tried, the policies didn't replicate properly as the default gpo from 2008 are a lot more restrictive than the 2003 ones. Before stopping the 2003 or transfering the roles or even allow it to authenticate users (using active directory sites and services), you need to be sure that everything is properly replicated on the new DC (login scripts/gpo = the whole sysvol). Also check that the 2008 DC policies after it is a computer member are set like the windows 2003 DC.

You most likely just need to add the needed roles on the 2008 server (if your active directory schema is already a the right level, if not you'll need to do adprep/forestprep/domainprep if needed) then make the server a domain computer of your 2003 domain then do the dcpromo then transfer the roles with ntdsutil (you can use other methods but that's the easier) on the 2008 DC. After everything is working properly on the windows 2008 DC, you'll be able to try shuting down for a while ( a few hours a least) the 2003 so you'll be sure everything is still working (except replication with the 2003 dc) then restart the 2003 DC and demote it from dc role.

Try this MS Technet article to separate the services running in this process and know which one is the culprit. Off course, you'll have to re-set them as shared after.

My prefered linux liveCD with ntfs prog is systemrescuecd.

If dotnet isn't needed for your server, you could try to remove it with the dotnet cleanup utility from MS and remove all dotnet > 2.0 as only 2.0 is integrated in 2008 R2. I hope this will help you to solve this.

For the record, CSS conditional comment only work for IE: http://www.quirksmode.org/css/condcom.html.

The machine.config is stored in the windows 2008 R2 Dvd, you can easily extract it using 7zip: - Open with 7zip the windows 2008 R2 iso (if you have it in the iso format else go to the next step) - Open the install.wim (stored in sources folder) with 7zip - go to "1\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\" and you should find the file you need.

The initrd given with avg contain this line mount -t ext2 -o loop /mnt/usb/arl_rootfs.ext2 /mnt/root So it is a linux ext2 ram disk image, i don't know any simple XP tool to do it. But with a linux livecd or a linux: you just need to create a mount point (for example: mkdir /mnt/avgmountpoint ) and then do mount -t ext2 -o loop path_to_/arl_rootfs.ext2 /mnt/avgmountpoint Then copy your files there with cp and then umount the ramdisk image (umount /mnt/avgmountpoint ).

I had the same kind of problem but only with the eventviewer snap-in. A simple reboot (despite the server was already restarted before) solved it but it might not help in your case. Does the problem happens with every snap-in ? Does it also happen when launching mmc and loading the snap-in ?

For the record autoit has a function to remove white space of any kind (tab included).

Or set the share permission to allow anyone (thus weakening a lot the security of the server hosting the share if the client and the server aren't member of an AD domain). But you might want to try this way but i find it worse.

Yes write should do the trick but you might want to do additional steps: - before doing write with testdisk, you should create disk image as explained there by Jaclaz. - do the write with testdisk - do a chkdsk /F or if you have more time /R of the partition.

I look like that your winpe (whatever its version) doesn't contain the mass storage driver for the virtual controller of your VM. Depending what you're trying to do, you'd need to add the virtual controller driver to your winpe or change your virtual controller type in your VM.

To my knowledge, when using the ctrl+alt+del interface instead of the welcome screen it will always ask for at least enter unless you enable autologon and sysinternals made a simple utility to help.

Also check in device manager, if there is a device with a yellow exclamation mark and if you used the front panel check if everything is properly connected to motherboard.

All of them can be safely disabled as they belong to the "Management Engine" functionality as long as you don't need to use those functionalities.

I would avoid mixing ram timing and voltage (that usually cause strange errors/crash) . I would either buy the same ram or renew all sticks and buy 2x4GB in this case.