It’s not difficult to create a local update server for SLES10 with OES2.
The tricky part is that in Yup (The update software who downloads the patches from Novell) can only handle one
service pack level. So if you define service pack level 1, Yup will only download the patches for SLES10 SP1 and OES2 sp1. Now we all know that this combination isn’t right. It’s SLES10SP1 with OES2 and later this year (Q4 of 2008) it will be SLES10 SP2 with OES2 SP1.
But let start at the beginning.
The Novell software updater can access Yup repositories via FTP or HTTP.
FTP Access
SLES10 come with a ftp server called vsftpd. Default only anonymous users can download from this server.
To configure Yup to store the update files in that directory, set
YUP_DEST_DIR=”/srv/ftp/yup”.
Be sure that this directories exists.
HTTP Access
Make sure that you have configured your apache webserver. Create a /etc/apache2/conf.d/yup-server.conf file with the content below:
<IfDefine yup_server>
Alias /yup/ /srv/ftp/yup
<Directory /srv/ftp/yup/>
Options +Indexes +FollowSymlinks
IndexOptions +Namewidth=*
Order deny,allow
Deny from all
Allow from YourSubnet
</Directory>
<IfDefine>
Edit the /etc/sysconfig/apache2 file and add yup_server to the APACHE_SERVER_FLAGS
So know we have a place to store and download our updates.
An Individual Desktop is great for users who require a singel unique dedicated desktop or for hosting a costly application with single host license that needs to be accessed by multiple users at a different time. Users how are entitled to this type of desktop always access this desktop each time the connect.
In order to deploy a Individual Desktop, this virtual machines has to have the VMware View Agent installed. Check here how you can accomplish this.
An Individual Desktop can be a Virtual Machine managed by vCenter or a physical machine. The last is great to provide remote access to a users physical desktop. Disadvantage is that it does not support Offline Desktop.
Deployment
- In the VMware View Administrator inteface, go to “Desktop and Pools“, click the inventory tab and click “Add“.
no images were found
- Select “Individual Desktop” and click on “Next”.
no images were found
- Select “VirtualCenter virtual machine. Supports Offline Desktop” and click “Next”.
no images were found
- Click on the vCenter server who hosts the Virtual Machine and click on “Next”
no images were found
- Enter a Unique ID (This is for Administrators), Display name (Users who use this desktop will see this name. If you don’t provide a Display name the Unique ID will be used.) and optional a Description.
no images were found
- Specify the desktop settings:
- State: Enabled (After being created the desktop is automatically enabled and ready to use), Disabled (After being created the desktop is not enabled. This is useful if you want to to post deplayment tasks.)
- When VM is not is use: Do nothing (VM remains on), Ensure VM is always powered on (if the user shutdown the desktop it’s immediately restarted), Suspend, Power off.
- Automatic logoff after disconnect: Never, Immediately or After (time in minutes when the desktop is logged off).
- Allow users to rest their desktop: User can without administrative assistance reset their desktop.
no images were found
- Select the Virtual Machine who you wanna use and click “Next”.
no images were found
- Review the options and click “Finish”.
An Automated Desktop Pool contains one one or more dynamically generated desktops that are automatically created and customized by View Manager from a vCenter virtual machine template. There are two types of desktops:
- Persistent: An user is assigned an dedicated desktop, who contains the users settings, documents and applications. This assignment happens the first time a user connects and is than used for all the user sessions.
- Non-persistent: When a user connects, they are assigned a different desktop from the pool every time they connect. There is no persistent data between sessions.
When we want to create a Automated Desktop Pool, we have to create a Virtual Machine Template in vCenter. To do so, right click on a Virtual Machine and select “Convert to template” or “Clone to Template”.
When you have a template, you must create a Customization Specification in order to deploy automated desktops.
Configuration
- In VMware View Administration, select on “Desktops and Pools” and click on “Add”.
no images were found
- Select the “Automated Desktop Pool” type and click on “Next“.
no images were found
- Select the Desktop Persistence. In my case: Non-persistent.
no images were found
- Click on the vCenter server who hosts the template. Notice that “Use linked clone technology to create desktops in this pool” is grayed out. To use this feature you will have to configure this on your vCenter server (PROVIDE LINK!!!!)
no images were found
- Provide a Unique ID (Example: Corporate Desktops), Display Name (Example: Standard Desktop WilmsenIT) and a description.
If you don’t provide a Display Name, the Unique ID will be used.no images were found
- Provide the Desktop/Pool Settings:
- State: Enabled (After being created the desktop is automatically enabled and ready to use), Disabled (After being created the desktop is not enabled. This is useful if you want to to post deployment tasks.)
- When VM is not is use: Do nothing (VM remains on), Ensure VM is always powered on (if the user shutdown the desktop it’s immediately restarted), Suspend, Power off.
- Automatic log off after disconnect: Never, Immediately or After (time in minutes when the desktop is logged off).
- Power off and delete virtual machine after first use: This is for Non-Persistent Pools only. When a users logs off, the Virtual Machine is deleted.
- Allow users to rest their desktop: User can without administrative assistance reset their desktop.
- Allow multiple sessions per user: This is for Non-Persistent Pools only. This enables users to make more connections to multiple desktops at the same time in the same pool.
no images were found
- Configure the desktop provision properties:
- Provisioning: Enabled (The desktop in the Pool will be immediately created upon completions of the deployment procedure or after a desktop is deleted), Disabled (The desktop in the pool will not be immediately created upon completion of the deployment procedure or after a desktop is deleted.).
- Number off Desktops: Specify the number of desktops created in this pool. This setting is disabled if you select the “Enable Advanced Pool Settings” check box in the “Advanced Settings” Panel.
- VM naming Pattern: By default, a prefix is used to identify all desktops in a pool as part of the same group. The prefix can be up to 13 characters in length and a numeric suffix is appended to this entry in order to distinguish each desktop from others in the same pool.
You can override thsi behavior by entering a name that contains a token representing the pool number {n} (Example: Finance-{n}-Desktop). You can add a fixed length token {fixed=3} (Example: Finance-{n:fixed=3}. The output can be: Finance-001 or Finance-002).
- Stop provisioning on error: This stops the provisioning of new virtual machines when error occur (for example no disk space left).
- Advanced Settings: Enable this option if you want to configure random provisioning. Give the number of “Minimum Desktops“, “Maximum Desktops” and “Availible Desktops“.
no images were found
- Select the Template who you wanne use. Make sure that the correct version fo Sysprep is installed on vCenter for this Template. After selecting the Template click “Next“.
no images were found
- Select the Place were the Desktop Pool will be created.
no images were found
- Select a host or a cluster where the Virtual Machine will run and click on “Next“. (Only Clusters of 8 hosts or less are supported and shown).
no images were found
- If you have a recourse pool, select it and click on “Next“.
no images were found
- Select one or more datastores where to store the Desktop Pool and click on “Next“.
no images were found
- If you want to use a specific Customization Specification select “Use this customization specification” and click on the Customization Specification you have created. If you want to customize the desktop manual select ” None – Customization will be done manually“.
no images were found
- Review the summary and if agree click “Finish”.
Now we are ready to automatically deploy desktops for our users.
Entitling a Desktop or a Pool in VMware View is pretty muts the same as giving Users the right to access a View Desktop.
- In the VMware View Administrator, click Desktops and Pools and then click on “Global desktop and pool view“. Under the “Global desktop and pool view” select the Desktop or Pool who you wanne entitle.
- Click on “Entitlements” and than on “Add”.
- Select your Domain search for the User(s) or Group(s) who you wanne give access to the Pool or Desktop. If you want to select a group. Don’t forget to mark the checkbox near Groups.
- Select the Group or User(s) and click on “Ok“.
- Optional repeat step 4 if you want to select more User(s) or Groups. Than click “Ok“
Make sure that the users have remote desktop rights to the Desktops that are entitled. This is done through Group Policies in the AD.
First some Theory!!
With the View Compsor on vCenter your able to create and deploy linked clone desktops.
A linked clone desktop are multiple dekstops create from one Baes VM, called the parent. The link is indirect because the first time one or more desktop clones are created, a uniquely identified copy of the parent VM (called a Replica) is created. All desktop clones are anchored directly to the replica and not to the parent VM.
The parent can be updated or replaced withoud directly affecting the linked clone desktops. You the parent can be Viewed a standonle VM.
Here a illistration of the relationships taken of the View Manager Administartion Guide.
PLAATJE!!!!
Because all linked clone desktops are connected to the one base image, you can centrilize your management on this desktop while maintaining a seamless user experience.
You can perform the following task:
- resetting a system to default
- balancing storage
- install software
- applying service packs
View Manager administrators can simultaneously update (or change) the operating systems of al linked clone desktops, install or update client applications, or modify the desktop hardare settings byr carrying out the activities on the Parent VM and then anchoring the linked clones to a new snapshot of this configuration. This action is called Desktop Recompositon.
A Desktop Refresh is returning the operating system data of each linked clone to its original state.
The initial disk usage of a linked clone virtual machine is far lower than that of a full clone because the operating system and client applications are derived from a Parent VM. This is accomplished through the use of delta disks and thin provisioning.
Every new desktop created in a standard (non-linked clone) automated pool is a duplicate of a base template. Therefore each clone uses as must disk space as its base template.
View Composer gratly reduces the physical storage overhead of linked clone desktop pools through use of delta disks. The disks growth deplends on factors such as workload, power-off policy pool type etc.
In the delta disk data is stored of the difference between its own operating system and the operating system of the Parent VM.
And now the installation of vCenter
- Run the View Composer service installation program, where is xxx is the build number of the executable file: VMware-viewcomposer-xxx.exe
Note: If not detected Microsoft .NET 3.0 will be installed
- Accept the file agreement and click Next.
- Accept or change the destination folder path and click Next.
- Enter the name of the ODBC Data Source you have create and the username and password for this database.
- Accept the default SOAP port and click Next.
- Click install
Next where going to prepare a Parent VM. XXXXXXXXXXXXXXXXXXXX
Uncategorized | Michael March 17, 2009 | 
Comments (4) 