Cisco VPN3000 webVPN configuration

The problem with CIFS access to share on a domain controller can be fixed by:
"It is also worth noting that it might be necessary to modify local policies on a Windows 2003 domain controller when configuring file access. Specifically, it might be necessary to open the Domain Controller Security Policy (found under Administrative Tools) and under Local Policies > Security Options disable the Microsoft network server: Digitally sign communication (always) policy (right-click and choose Properties)" - it should be disabled on a domain controller with shares.
additional link: http://www.networkworld.com/subnets/cisco/072507-ch10-deploying-vpns.html?page=4

Adobe Flash player and Citrix (WTS)

Install Flash Player as ActiveX with "change user /install" mode, edit permissions on the keys (below) and deleted IE application and published it again:

HKEY_CLASSES_ROOT\CLSID\{D27CDB6E-AE6D-11cf-96B8-444553540000}

HKEY_CLASSES_ROOT\CLSID\{D27CDB70-AE6D-11cf-96B8-444553540000}

1. Right-click the key, select "Permissions"
2. In the Permissions Dialog click the "Advanced" button
3. Click "Add"
4. Enter "Everyone" and click "OK" to accept
5. Select "Allow" for the "Query Value", "Enumerate Subkeys", "Notify" and "Read Control" permissions.

WVS from VS 2005 conversion

from http://faq.windowsvirtualization.com/
"Currently, there is no direct import capability, so it’s largely a manual exercise. A Virtual Server VM consists of a configuration file (.vmc) and one or more data files such as Virtual Hard Disks (VHDs) and other media such as .ISO and .VFD. For the purposes of migration, it’s the VHDs which are the most important ones as these obviously hold the important data.

If your VM is using a shared SCSI bus as part of a test/dev cluster, stop now. You will have to break your cluster, migrate one node and move to an alternate form of shared storage such as iSCSI for migration. That’s a blog post for another day and I won’t be covering that in this post.

…

The first real consideration is the Virtual Machine additions which will likely be installed in your VM. If they are, it’s may be easier to remove them before bringing the VM into WSv. If you know you have the latest version of the VM additions from VS 2005 R2 SP1 (v13.813), you can uninstall the additions when the VM is booted under WSv, but earlier versions of the additions may fail to uninstall when booted under WSv. If you’re unsure of which version you have installed, it’s best to uninstall while you have a working VM under Virtual Server. Once the additions are uninstalled, make sure the VM is shut down, not saved. Saved states are not compatible between Virtual Server and WSv.

Now copy all the VHDs configured in your VM across to your server running WSv. Let’s assume for the time being that this is the simplest case where there is a single VHD for the VM. Simply walk through the new virtual machine wizard and attached the existing VHD. Easy, yes?

If you have more VHDs to add, at the end of the wizard, choose to not start the VM. Instead, open the settings for the newly created VM and add each VHD in turn to the configuration. If you need more than four VHDs (or three plus a CD/DVD), attach a SCSI controller and attach the remaining VHDs to the SCSI controller instead.

You may now have some questions. The one I’m particularly thinking you’ll ask is what if my VM under Virtual Server was booting from an emulated SCSI controller, not from IDE. The answer is relatively long winded and I’ll explain another day, but if that is the case, attach the boot VHD to the IDE controller 0 at location 0. It should still boot. The less obvious one question was what if my boot VHD was on SCSI and is > 127GB in size? Again, the answer is for another day. Just use IDE and trust me!

If the VM is not yet running, start it, connect to it and login. You will probably be presented with the new hardware wizard. Cancel it by pressing escape for now. As an interesting experiment, especially if you ended up adding drives to a SCSI controller, you’ll notice that they won’t show up yet in Disk Management or Explorer. That’s because you don’t yet have the drivers installed for the “synthetic” SCSI controller. They will be installed with the Integration Components.

Insert the Integration Components CD from the Action menu option in the Virtual Machine Connection application. It should auto-play, but if not, run setup.exe from the \support\x86 directory. Follow the prompts and reboot as requested. On completion, your VM should be good to go.

One other point for Windows Server 2003 VMs, I would strongly recommend you upgrade to SP2 if you haven’t already to gain the maximum benefits of running under Windows Server virtualization. Otherwise, go have fun!"

WTS registry adjustments

1. Configure the Server Service’s Memory Management. This setting will benefit the server to maximize memory for Network services and can be found :

Local Area Network properties > File and printer sharing > server optimization > than check “maximize data throughput for network applications”

these settings can be modified with registry key

HKLM\CurrentControlSet\Control\Session manager\memory management > “LargeSystemCache” = “0”

HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters > “Size” = “3”

2. Disable Dr. Watson popup

HKLM\CurrentControlSet\Controls\Windows> “ErrorMode” = “2”

3. Disable paging of the Windows NT executive.

Microsoft Article Q184419, Q323608

4. Disable print events from the Event log.

HKLM\System\CurrentControlSet\Control\Print\Providers >

For no printer logging set “EventLog” = dword:00000000

To log errors only, set “EventLog” = dword:00000001 (I usually do errors only)

5. Disable roaming Profile Cache

HKLM\Software\Microsoft\Windows NT\CurrentVersion\winlogon >

“DeleteRoamingCache” = dword:00000001

6. Disable the printer beep to reduce bandwidth and increase performance.

HKLM\System\CurrentControlSet\Control\print >

“beepEnabled” = dword:00000000