I upgraded our environment from 3.0.1 to 3.1 in about an hour, granted our environment was fairly new and we hadn't really gotten too far into the demo we had. We did have the composer software i...
See more...
I upgraded our environment from 3.0.1 to 3.1 in about an hour, granted our environment was fairly new and we hadn't really gotten too far into the demo we had. We did have the composer software installed and it upgraded with no issues. All I did was install the 3.1 software right over the 3.0.1 software and upgrade the agents. Like I said though, we hadn't done anything really with our environment. We had just started trying to use linked clones and ran into an AD issue and upgraded to "fix" that issue.
Mark, Are you using View 3.0 ? If so, then upgrade to 3.1, that made it possible for us to use our "single label" domain name. i was able to install 3.1 right over the top...
See more...
Mark, Are you using View 3.0 ? If so, then upgrade to 3.1, that made it possible for us to use our "single label" domain name. i was able to install 3.1 right over the top of our 3.0 installation.
I am not sure if we are connecting to our View environment through a Juniper SSL VPN but we do connect to our environment through SSL VPN. Once we have established a connection to the SSL VPN ...
See more...
I am not sure if we are connecting to our View environment through a Juniper SSL VPN but we do connect to our environment through SSL VPN. Once we have established a connection to the SSL VPN device we are presented with a webpage and one of the links on that webpage is to our View Connection server. When we click on that link we are taken right to our Connection server where we have to authenticate and then the rest of the connection is normal from there. I can't speak for the setup of the SSL VPN device as we don't have control of that part of our network. I do know that we spent about a week getting it setup so that it would work. I'm sorry that I can't provide you with any specifics on the setup as we were not involved in the details of any changes that needed to be made to make the connection work.
That explains why my Windows 7 with IE8 doesn't work from home. We only have access setup to go through the web. I breezed right on by that section when we were setting up our POC. ...
See more...
That explains why my Windows 7 with IE8 doesn't work from home. We only have access setup to go through the web. I breezed right on by that section when we were setting up our POC. I may have to try downloading IE7 and see if that works at home for me.
Peter, We are just in the demo phase at this time and waiting to see if management wants to use this software for our home agents. If they do then we are looking at possibly 30-50 users to ...
See more...
Peter, We are just in the demo phase at this time and waiting to see if management wants to use this software for our home agents. If they do then we are looking at possibly 30-50 users to start. If that happens we will be using our current setup to start. ESX Hosts: 3 IBM HS20 blades 3.2Ghz 6 GB RAM IBM DS800 SAN LUN Connection Server: 1 vCPU 4 GB RAM 30 GB HDD Thank you, Joel C. Butler NYS Departmant of Labor Planning and Technology Information Technology Specialist II T: 518-457-9099 Joel.Butler@labor.state.ny.us
Peter, I would start with one vCPU and expand if you need to. We have seen where 1 vCPU is plenty depending on the processor you have in your ESX host. Thank you, Joel C. Butler NYS ...
See more...
Peter, I would start with one vCPU and expand if you need to. We have seen where 1 vCPU is plenty depending on the processor you have in your ESX host. Thank you, Joel C. Butler NYS Departmant of Labor Planning and Technology Information Technology Specialist II T: 518-457-9099 Joel.Butler@labor.state.ny.us
Hey Peter, Take a look at the View Manager Administration Guide on page 14 for the system requirements. I would make sure the connection servers have at least 4GB RAM as it states t...
See more...
Hey Peter, Take a look at the View Manager Administration Guide on page 14 for the system requirements. I would make sure the connection servers have at least 4GB RAM as it states to have 3GB or more for 50+ connections.
Just a thought - have you logged out of the View Portal and back in since you have added the desktop to the pool ???? as mjsvirt said is this user also in the Remote Desktop Users group on the...
See more...
Just a thought - have you logged out of the View Portal and back in since you have added the desktop to the pool ???? as mjsvirt said is this user also in the Remote Desktop Users group on the actual VM that you added to the pool ??? just had an issue where I forgot to add the proper group to the remote desktop users group and had to log out of the Portal and back in to see the change.
We were having an issue that was similar to this in that we were seeing the desktop in the pool as ready but then once we logged in and disconnected we were getting the customization timed out ...
See more...
We were having an issue that was similar to this in that we were seeing the desktop in the pool as ready but then once we logged in and disconnected we were getting the customization timed out error. our problem was US :smileysilly: as we don't have a DHCP server on the network segment we are using for our View testing and we can not have a DHCP server on that network segment. We are manually assigning IPs to the desktops until this goes to production and we can set up a network segment with a DHCP server on it. We also had the the pool setup to refresh the OS disc on disconnect at which point it set the IP address back to DHCP and no address. Once we entered the IP addresses everything was ok again, until the next disconnect. We have since changed our pool to NEVER reset the OS disk.
DNS is working correctly as I can get to the server by name or IP. Did upgrading to 3.1 fix the problem ? Like I said in the original post, we have very limited abilities in our domain. I...
See more...
DNS is working correctly as I can get to the server by name or IP. Did upgrading to 3.1 fix the problem ? Like I said in the original post, we have very limited abilities in our domain. If the upgrade fixes the issue I would give it a try but I don't want to introduce a "secondary issue" into the mix at this time. We are able to deploy VMs from a template with no problems and they work great so far, but we want to try linked clones and this part of the setup is stopping us.
I am looking for some help with an issue that we are running into with View Composer. At the end of this post is a blurb from the bottom of page 108 on the view administration guide. Our do...
See more...
I am looking for some help with an issue that we are running into with View Composer. At the end of this post is a blurb from the bottom of page 108 on the view administration guide. Our domain is not fully qualified (we do not control the domain and have limited management ability) and we are unable to enter the information in the View Composer Settings screen. We have tried a couple different ways to enter the domain name (IP and the name we see) and we get back that it is a bad domain name every time. I have checked the posts here looking for someone that may have had this issue in the past but I didn't find anything. Has anyone run across this before and have any insight for me regarding this issue ? Our environment: IBM HS20 blades (3) with Intel processors ESX 3.5 u4 Virtual Center 2.5 u4 View 3.0.1-142034 composer 1.0.0-126338 View Connection server 3.0.1-142034 Deploying Linked Clone Desktops from View Manager View Manager can only deploy linked clone desktops if it is able to communicate with a properly configured VirtualCenter host that is running the View Composer service. In addition, your Active Directory forest must have a fully qualified domain name, for example, example.com-you cannot use View Composer in environments where the domain controller has an unqualified name.
Christoph is right with the ViewManagerAdmin guide. I followed that once I had some networking issues on the View VC server figured out, it was smooth and we were able to deploy a test View De...
See more...
Christoph is right with the ViewManagerAdmin guide. I followed that once I had some networking issues on the View VC server figured out, it was smooth and we were able to deploy a test View Desktop in no time. Our ESX 3.5 servers were three IBM HS20 blades that were our dev environment. I had upgraded (not a clean install as others had suggested - it is only dev) the blades from 3.0.2 and the upgrade was flawless. The ESX 3.0.2 install was just a plain install without anything special done to them. As View is a POC for us at the moment we are testing with this one desktop before we roll out the "live" test desktop(s). There is another document for deploying XP desktops that I found here: . I am sure it would apply to all desktops that were being deployed.
