Posts tagged windows
There are many use cases for hiding system drives, whether it be with View, XenApp, or whatnot. Fortunately, there are already templates in place to accomplish hiding the system drives; it is just a matter of finding them and enabling them. First, you need to create a GPO to restrict access and to actually hide the drives. This will be a User GPO, but it will need to be in the Machine container of the computers in question.
Create a new GPO, browse to User Configuration->Policies->Administrative Templates->Windows Components->Windows Explorer. You will see 2 settings that are pertinent here:
- Hide these specified drives in My Computer
- Prevent access to drives from My Computer
Enable both of these, and select which drives you would like it to apply to.
The tricky part here is that the above is a User GPO, but it is applied to a Machine container. To make this GPO activate, User Group Policy loopback processing mode needs to be enabled. This policy directs the system to apply the set of GPOs for the computer to any user who logs on to the computer. This can be found in Computer Configuration->Policies->Administrative Templates->System->Group Policy.
Once done, restart the servers and test. The following is an example showing Microsoft Visio published through Citrix XenApp.
By default, this will apply to all users. To disable it for certain users, modify the Security settings of the GPO to not apply to the users in question (Microsoft KB 315675).
VMware has done a wonderful job making converting your existing infrastructure as painless as possible, but there are still issues that pop up every now and then. I find these issues occur much more often on Windows 2000 due to its age. We’ve ran into two issues recently on a couple of conversions of machines that now fall under our division’s management, and the worst part of these is that you only know about them after the conversion is done and you try to boot up your new VM. Fortunately, they are easy fixes:
VM boots with Blue Screen stating STOP 0x0000007B INACCESSIBLE_BOOT_DEVICE
This occurs because the newly converted VM does not have the necessary drivers to boot, and it is an easy fix (KB Article: 1005208).
- Power on the source for the conversion. The source can be physical or virtual.
- Download the VMware SCSI Disk Controller driver diskette at http://download3.vmware.com/software/vmscsi-220.127.116.11.flp.
- Extract the disk image into files and copy them to the source.
- Attach the diskette to a virtual machine and copy the files from the virtual diskette drive to the physical source.
- Write contents of the image onto a floppy diskette and insert the diskette into the physical source. Image extraction software is required to do this.
- Access the floppy diskette or files on the source from My Computer.
- Right-click vmscsi.inf and click Install. The VMware SCSI drivers are installed.
- Restart the source to complete installation.
- Perform another conversion with VMware Converter
Converted machine fails to power on with the error: Stop:0X0000001 KMODE_EXCEPTION_NOT_HANDLED
This is actually Microsoft’s fault. The resolution is covered in Microsoft’s KB 904374.
They provide the resolution on the basis that someone received this problem on their machine and then rebooted and now they can’t boot any longer. You can proceed with their instructions exactly, and repair the VM that you’ve already converted. Or, if you prefer an easier method, you can request the Hotfix download from Microsoft and install it on the Physical source then simply retry the conversion and it should work properly.