Posted on 29. Oct, 2011 by in View Install Guide.

 

Quick Recap of what we’ve done so far:

The next part of the Connection Broker install is to setup your vCenter and Composer credentials.    As with a lot of VMware’s new management user interfaces, everything is moving towards a Adobe Flex client to manage.  This is great because it frees you up from having to install management applications on your device.  It also makes it really handy to manage your View environment from just about any browser in any VM you happen to be in !!  VERY COOL.  Anyway, lets get back to the topic at hand. 

Here is a quick list of things I’ll be taking you through during this part.

  • We will add our vCenter Credentials into View Manager.
  • We will hop over to our AD server and setup a new Organizational Unit and create 2 new Groups to manage.
  • We will add one of the groups (Admin) to the View Manager Admin group.

 

1. First lets log in to the View Administrator console. You can do that from a any computer/browser that is on your network.  Simple point to your ViewServer name with a /admin at the end.

 

2 - Log into Connection Server

 

2. This is your main admin screen.  This is where you will spend a lot of your time managing your VMware View 5 environment. 

3 - Main screen when you log in

3. Let’s add our vCenter credentials into View – Expand the View Configuration Information and then click Add under the vCenter Servers area.

4 - expand View Config and click Servers

4. Enter in your vCenter information and credentials.  Once you have that populated you should see a small hour glass and then you can click on Enable View Composer which we installed in a previous blog post.

5 - Add in the following info

5. For the composer information, just put in your domain info, no need to add the server name.  Then enter in the vCenter credentials again since that’s where it’s installed.

6 - for composer setup - enter in domain name and username-password

6. When you are done, you should see your vCenter information populate under the vCenter Servers area. 

7 - done with adding vcenter info

Setting up new OU and Groups in AD

Adding an Administrator group can be very handy if you have multiple people that need to have this level of access.  The easiest way to manage these users is through a group.  First thing you need to do is log into your Active Directory server and setup a few things:

1. RDP into your AD server and click on Start/Programs/Administrative Tools/Active Directory Users and Computers.  Then right click on your domain, click on new and add an Organization Unit.

50 - Create new View OU Group2. In this case, I’m going to add an OU called View 551 - name your OU View 5

3. Once you are done with that, lets right click on that new OU and go to New – Group and create a new Group inside the OU

52 - Create a new Group - Admins


4. I’m going to create 2 groups for now.  One for Admin’s and one for general users.  This way when I start to “entitling” users to desktops I can use a group instead of individual names.

53 - Create View5GroupAdmins

5. When you are done you should see 2 new groups.

54 - Create another group for users

6. Lets add some users into the groups so double click on a group and click Members and then ADD and add a couple of users.

55 - Double click on the admin group and add a couple of admins

7. Do the same thing for the View5Users group.

56 - add users to the view5 user group


Now lets go back to our View Admin screen and add the new View5Admin group to the list of admins on the console.


1. A couple of lines below the place we added the vCenter info is the Administrators link.  Click on that.

10 - we need to add users and groups to the group

2. Click on the Add User or Group button

11 - add users groups

3. Click on the Add button on the bottom of the screen

12 - click on add

4. Do a quick search for View and that should populate some information below.  In this case I’m going to just select the View5GroupAdmin one. Then click OK

13 - lets just add the admin group for now

5. You should now see that group added to the list.  Click next

14 - noticed the admin group was added - click next

6. Here is where we can assign the level of permissions we want to give this group.  In my case I simply gave them Admin level – you can pick and choose depending on your use case.

15 - click on the admininistrators role and click next

7. Check the box to give the admin group rights to the root.

16 - Check the box for root - and then finish

8. Now you should see your group added.

17 - validate that we are good to go


Easy Peasy

 

So now that we have the Connection server all squared away, we need to go create our desktop to use.  Let’s move on to “Installing View 5 Desktop Agent in Windows 7 64bit OS”.

@vTexan



 

 

 

Facebook Twitter Linkedin Email Snailmail

6 Responses to “Setting up View 5 Connection Server for the 1st time”

 
  1. [...] Trogden – Setting up View 5 Connection Server for the 1st time – The next part of the Connection Broker install is to setup your vCenter and Composer [...]

  2. Joe says:

    i was stuck for so long at the login screen, something happened in my test server environment where the local administrator was not part of the domain admins, so I was not able to logon to my view server using the domain – uninstalling and reinstalled AD corrected it.

    This guide is fantastic.

  3. L H says:

    Not sure if this is a new issue in 5.1… the following happened to me:

    The solution came from the following web site to make sure credit is given where it is due :-)
    http://blogs.virtualizationadmin.com/lowe/2010/09/28/learn-from-my-mistake-a-vmware-viewcomposer-basic-issue/

    I got the View Connection Server up and running with no problems. On the connection server, I had no issues whatsoever specifying the name and credentials for my vCenter server. However, when I attempt to Enable View Composer, I get the error message “Error while attempting to connect to View Composer” with no more detail. I searched through logs, but, for the life of me, could not figure out what I was doing wrong. I even went so far as to uninstall and reinstall the Composer tool on the vCenter server to make sure I hadn’t overlooked anything.

    So, what had I done wrong?

    When specifying the user name and password to use with the vCenter server, I failed to use the domain\user format. I had simply provided the user name. It worked for connecting to vCenter but did not work for the View Composer. Once I change the username to the right format, everything began to work as expected.

  4. ethan says:

    hi vTexan have you tested out this problem? I also having the same problem while i tried to connect to view composer.


Leave a Reply


 

wordpress visitors
The opinions expressed here are my personal opinions. Content published here is not read or approved in advance by EMC and does not necessarily reflect the views and opinions of EMC nor does it constitute any official communication of EMC.