mikebarnett's Accepted Solutions

Ah, I see. Yes, once the Parent VM has been started on the new hardware both CPUs will exist in Windows. Windows won't clean up the old one so it will remain in place preventing the message from ... See more...
Ah, I see. Yes, once the Parent VM has been started on the new hardware both CPUs will exist in Windows. Windows won't clean up the old one so it will remain in place preventing the message from appearing again. -Mike
Hello DS, To use the Blast protocol you must have both port 443 and 8443 open. Port 443 is used to server the View portal for users to download the thick client as well as access the Blast cli... See more...
Hello DS, To use the Blast protocol you must have both port 443 and 8443 open. Port 443 is used to server the View portal for users to download the thick client as well as access the Blast client login. Port 8443 is the port used to tunnel the Blast traffic through the Security Server or Connection Server to the end desktop. These are different services and require different ports. Both connections are secured via SSL. -Mike
The setting you're looking for is the AllowSingleSignon policy. Disabling this will cause the VM to require reauthentication at the desktop and will enable the use case you're looking for. Det... See more...
The setting you're looking for is the AllowSingleSignon policy. Disabling this will cause the VM to require reauthentication at the desktop and will enable the use case you're looking for. Details on this setting can be found here: View Agent Configuration ADM Template Settings You will need to install the View Agent ADM template in AD and apply this policy for it to be active. You can also assign the template to just the single VM if needed. -Mike
'View Manager' is simply the old name for the VMware Horizon View product. The iteration of names was something like; VMware Virtual Desktop Manager 2.0 VMware View Manager 3.0 VMware View 4... See more...
'View Manager' is simply the old name for the VMware Horizon View product. The iteration of names was something like; VMware Virtual Desktop Manager 2.0 VMware View Manager 3.0 VMware View 4.0 -> 5.1 VMware Horizon View 5.2 Looks like the doc team hasn't changed that reference yet. It should just read 'we can add vCenter Server instances to View through View Administrator. -Mike
As Mark says, you can disable Single Sign-on on the desktop so that after you authenticate to View (this will have to be a domain user) you can then enter whatever credentials you need to on the ... See more...
As Mark says, you can disable Single Sign-on on the desktop so that after you authenticate to View (this will have to be a domain user) you can then enter whatever credentials you need to on the desktop itself. Details on the policy are in the View 5.1 Admin Guide on Page 163 and the policy is titled AllowSingleSignon: http://pubs.vmware.com/view-51/topic/com.vmware.ICbase/PDF/view-51-administration.pdf You could also take this one step further. After you have disabled SSO on the desktop you could set up kiosk mode in View so that the client used to connect to this desktop (if you're only using a single client) would connect up to that desktop automatically and then the user would simply see the Windows login prompt and be able to authenticate locally.
If your ESX hosts are added to vCenter by hostname and your vCenter is added to View by hostname you should be able to make this change without impacting View. If your vCenter is added by IP t... See more...
If your ESX hosts are added to vCenter by hostname and your vCenter is added to View by hostname you should be able to make this change without impacting View. If your vCenter is added by IP then you will run into issues. If your ESX hosts are added by IP then you can use maintenance mode to migrate all VMs off each host, remove it from inventory and then add it back to the cluster using the new IP or hostname. View should have no issues with this as we don't reference the hosts by their hostname in any kind of static way. -Mike
Unfortunately we can't directly provide console access to RDP sessions because of the way that RDP connections work. RDP actually spawns a separate virtual session that the user connects to wh... See more...
Unfortunately we can't directly provide console access to RDP sessions because of the way that RDP connections work. RDP actually spawns a separate virtual session that the user connects to which causes the vSphere console to show a locked screen. When PCoIP runs it is spinning up a server process which hooks into the virtual video card of the virtual desktop. We use the Agent to log the user in and then connect the PCoIP session directly to the video card of that console session through the network. I don't know if there are any plans to develop some sort of specific shadowing that would support both RDP and PCoIP. -Mike
The closest printer is determined by a set of rules that you configure in the Location-based printing GPO. Essentially you configure a rule that should correspond to a particular user, group, IP,... See more...
The closest printer is determined by a set of rules that you configure in the Location-based printing GPO. Essentially you configure a rule that should correspond to a particular user, group, IP, MAC or range of IPs/MACs which will map the closest printer to that configured setting. For a Marketing group you would configure the printer in the Marketing area. For a printer in a certain area you could configure the clients nearby to all be in the same subnet and then configure that subnet range to map to the close by printer. Let me know if you have more questions. -Mike
There shouldn't be any issues when going from 32-bit to 64-bit for an upgrade here. My best recommendation would be simply to create a new 64-bit 2008 R2 server and install a replica 4.6 Conne... See more...
There shouldn't be any issues when going from 32-bit to 64-bit for an upgrade here. My best recommendation would be simply to create a new 64-bit 2008 R2 server and install a replica 4.6 Connection Server there pointing to one of the 32-bit Connection Servers. Then uninstall the 4.6 Connection Server on the 32-bit server. Once you have only the 64-bit server left you can upgrade it to View 5.1. Then, if you need to have the old hostnames or you want additional servers you can spin up 64-bit versions with the correct hostname and install them as replicas of the server you upgraded. Backing up all of the components involved in a View cluster is always a good idea in case you need to restore at any point. With backups taken around the same time you know you will be restoring to a consistent data set. Automatic backups of the View Connection Server information should be occurring automatically each day at 12am if you haven't changed any default settings. You can check this under View Configuration>Servers in the Connection Servers section. There should be a Backup field which should show the timestamp of the last successful backup. I believe you can edit these settings by selecting the Connection Server you want to edit and clicking the Edit button. -Mike
I know you can do it with VBScript. The following two links will hopefully get you started: http://www.activexperts.com/network-monitor/windowsmanagement/scripts/otherds/adam/retrieving/ ht... See more...
I know you can do it with VBScript. The following two links will hopefully get you started: http://www.activexperts.com/network-monitor/windowsmanagement/scripts/otherds/adam/retrieving/ http://technet.microsoft.com/en-us/library/cc758446(v=ws.10).aspx As long as the script is running as a local admin user on a Connection Server you should be able to bind to the server and run the queries necessary to get the info. The relevant areas you will want to look are: OU=Servers <-This contains a reference for each virtual desktop OU-Server Groups <-This contains a reference for each pool Under each desktop object you will want to look for the status attribute and the maintenance mode attribute to get more info. The best way to get familiar with what you're looking for is to log into ADAM using ADSIedit and poke around the above areas. That way you can see which object you're looking at by using the pae-DisplayName attribute and compare the status it's in with what is displayed in the attributes for that object. Hopefully this helps get you started! -Mike
It's not possible to change the name of existing desktops by editing the pool settings. There is no way to cause this to occur automatically and doing this manually would not make View happy. ... See more...
It's not possible to change the name of existing desktops by editing the pool settings. There is no way to cause this to occur automatically and doing this manually would not make View happy. Unfortunately, for dedicated pools you will have more work to do. If you aren't using Persona then you will have to detach the persistent disks and recreate VMs in the pool with that disk to cause a new VM with a new name to be spawned. If you are using Persona you could just delete all of the VMs and have Persona pull the profile data back down to the VM that the user would be entitled to when they next log in. This will cause all user installed programs to go away but hopefully this isn't common if you are already using linked-clones. I would encourage you to go to the following page and click the Feature Request form link and post information about what you're trying to do: https://www.vmware.com/support/policies/feature.html Notifications about features are reviewed by VMware and if you can get enough of your friends/fellow View users to ask for something often a solution will be developed in some way, shape or form. Hopefully this helps. -Mike
That KB should get you fixed up once you can connect to ADSI edit. Make sure when you are connecting that you explicitly define the server you're connecting to as localhost. If you let it auto... See more...
That KB should get you fixed up once you can connect to ADSI edit. Make sure when you are connecting that you explicitly define the server you're connecting to as localhost. If you let it autodetect it will connect to one of your AD controllers instead of the View AD LDS instance.
Unfortunately, you are correct. There is currently no 3d acceleration on View VMs. Sorry I can't provide any further help! -Mike
To add to this slightly, we do not support the View Connection Server being installed on the same server as vCenter or any other View component. It must be on its own separate server. -Mike
Are you using RDP or PCoIP? RDP will use the built-in drive redirection and should work but PCoIP does not support this feature yet. -Mike
Have you installed and setup a Transfer Server? -Mike
Hi Aaron, Yes, the Connection Server and Transfer Servers must be separate servers. As a general rule no View Component can be installed on a machine that has another component installed on it... See more...
Hi Aaron, Yes, the Connection Server and Transfer Servers must be separate servers. As a general rule no View Component can be installed on a machine that has another component installed on it. Hope that helps! -Mike
What firmware are you running with? Our HCL does list firmware 7.0.30 as the certified one for View 4.5. -Mike
It is likely that you don't have full DNS resolution between the two domains. It’s not enough to simply be able to resolve the name of the DC. You must have full resolution between the two domain... See more...
It is likely that you don't have full DNS resolution between the two domains. It’s not enough to simply be able to resolve the name of the DC. You must have full resolution between the two domains. -Mike
Ah, I see. If you have the Enterprise edition of View 4.5 then you do are not licensed for View Composer and you won't be able to download it. If you have View Premier then you will have to go to... See more...
Ah, I see. If you have the Enterprise edition of View 4.5 then you do are not licensed for View Composer and you won't be able to download it. If you have View Premier then you will have to go to that download section and try again. -Mike