• Open the server.xml file located in C:\Program Files\Citrix\Licensing\LS\conf\
• There should be an entry that begins with <user firstName=”System” id=”admin”…
• Replace the contents between the quotes of password=”" and replace it with a simple plain-text password. This is only a temporary password. The contents will be encrypted
• Change passwordExpired=”false” to passwordExpired=”true”
• Save and close the xml file
• Restart the Citrix Licensing Server Service
• Log into the Licensing Console using the username admin and the password you set in Step 3
• You should be prompted to reset the password upon logging in
• Re-open the server.xml file and verify that the password=”password you set” is now an encrypted string representing the new password you just entered

Good luck!

The post RESETTING CITRIX LICENSE SERVER PASSWORD appeared first on eGroup.

mirroring_role being equal to 1 indicates it has the PRINCIPAL role where the mirroring_state being equal to 4 indicates it is SYNCHRONIZED.

The procedure should be run on the server where the database is the PRINCIPAL. Running it on the MIRROR server will not result in any changes. Using Linked Servers and 2 parameters in the Stored Procedure such as:

sps_FailoverMirror (@databaseName nvarchar(200), @serverOne nvarchar(200), @serverTwo nvarchar(200))

would allow the Stored Procedure to query both servers, find the PRINCIPAL server, and perform the failover.

The post QUICKLY FAILOVER SQL SERVER MIRROR DATABASE appeared first on eGroup.

To identify the the database to work with one can either use the Mailbox name or the Mailbox GUID. To obtain the GUID run the following Exchange Management Shell command:

Get-MailboxDatabase -Identity “MailboxName” | Format-Table Name, GUID

Taking the resulting GUID, or the Mailbox Name itself, it can be plugged into the Identity property of the following command:

Move-DatabasePath -ConfigurationOnly -Identity “GUIDorName” -EdbFilePath “C:\PathToEdb\FileName.edb” -LogFolderPath “C:\PathToFolder”

The -ConfigurationOnly property instructs the Exchange Management Shell to ignore the fact that it cannot find the current path or file. The above command without the -ConfigurationOnly property is identical to running the Move Database Path option within the Exchange Management GUI.

Once the above command is complete, the Mailbox database can be mounted at which time it will create a new, empty, .edb file in the new storage location.

This is a nice command to have in your brain bank when faced with a situation where the existing path for your mailbox stores cannot be contacted or you’re restoring Mailbox databases to a new location.

The post EXCHANGE 2010 – CHANGING MAILBOX DB LOCATIONS WHEN DB IS UNAVAILABLE appeared first on eGroup.

By now we’ve all experienced the issue wherein any templates containing a network adapter configured to used a vNetwork Distributed Switch will cause the XenDesktop Wizard to crash when attempting to query available templates. The real kicker to this issue is that if any storage in the chosen DesktopController host configuration contains a template with a Distributed Switch then the behavior will appear. It does not matter if those templates are part of another vSphere installation, only that they are sharing the same storage.

Continue reading for more details and a PowerCLI based solution.

Here is the error received:

The supported solution from Citrix is to choose a template that has a Standard Switch configured (as should ALL templates located on the shared storage), begin the PVS XenDesktop Wizard and immediately before clicking finish to begin machine creation – convert the template back to a VM, change the adapter network to the desired distributed switch, and then convert back to a template. The problem is that I have personally seen this work approximately 25% of the time. It is a clunky solution to a known problem.

My solution was to craft a PowerCLI script to check each VM (based on a particular name format) in a vCenter instance for a particular standard switch (created and named for this particular issue), and change the Network Adapter network to the desired Distributed Switch.

Here is the script:

This will print out each VirtualMachine name that it discovers based on the search pattern. If the Network is changed it will also print out all of the relevant information after the change.

Word is this issue will be fixed as of PVS 6 which is due out in August or September – this issue has been around far too long to be waiting for a major release for a fix. It is critical functionality and while not more than an inconvenience when creating 5 machines, it is a huge pain when creating 500.

The post CITRIX PVS 5.6 XENDESKTOP WIZARD TEMPLATE ISSUE appeared first on eGroup.

The user having the issue was utilizing a Mandatory Profile created in Windows 7 that was launching from a shared network location. When running Outlook as Administrator the application launched correctly.

An attempt was made to use a PRF to auto configure the Outlook Profile but this produced the same error.

Outlook also failed to launch using any of the typical command line switches such as /resetnavpane, /safe:1, /safe, etc.

Click below to read more about the solution to this issue.

When removing the Mandatory Profile from the users AD Account and clearing the profile off of the XenApp server Outlook launched correctly.

The cause of this issue was that the user was unable to access a necessary key in HKCU that stores Profile Information. This was the reason mail.cpl was unable to launch and thus so was Outlook. It was preventing the creation of the profile for that user.

The solution was to rename the NTUSER.man file back to NTUSER.dat, load the hive into the registry and rename or delete the following key:

HKCUSoftwareMicrosoftWindows NTCurrentVersionWindows Messaging Subsystem

After doing this, the hive was unloaded and the file renamed back to NTUSER.man and copied back into the Mandatory Profile folder in the shared network location.

After re-launching Outlook both from XenDesktop and XenApp it was able to successfully start and a profile was created. In reviewing HKCU in the registry it was noted that a new Key was created to replace the one removed from NTUSER.man and it was accessible to the user. The mail.cpl applet was also able to be launched by the user.

The post Outlook 2010 “Unable to Open” – XenApp 6 – XenDesktop 5 – Mandatory Profiles appeared first on eGroup.

The solution involved several changes to the XenDesktop registry to work seamlessly

File type association was configured in the Application Properties under Advanced -> Content Redirection.

Create or Edit: HKEY_LOCAL_MACHINE SoftwareCitrixUncLinksUNCEnabled and ensure it is set to DWORD 0.

Create or Edit: HKEY_LOCAL_MACHINESOFTWARECitrixICA ClientEngineConfigurationAdvancedModulesClientDrive and ensure it is set to REG_SZ TRUE.

The registry changesadditions were pushed using a machine startup policy in AppSense Environment Manager.

Related Citrix KB Articles:

CTX238200

CTX126763

The post ISSUES LAUNCHING XenApp APPLICATIONS DELIVERED TO XenDesktop – Mapped Drives appeared first on eGroup.

Once you’ve configured port access for remote assistance through Desktop Director – 3389 and 5985 – don’t forget to apply the required group policy to the desktops. This can be done through local policy or to the newly created GPO applied to your dedicated VDI OU.

Computer Configuration -> Administrative Templates -> System -> Remote Assistance -> Offer Remote Assistance.

Make sure to enable this object and also configure those allowed to perform the remote access.

The post XENDESKTOP 5 AND USING REMOTE ASSISTANCE THROUGH DESKTOP DIRECTOR appeared first on eGroup.

Exception of type System.Data.SqlClient.SqlException caught, error=MODIFY FILE failed. Specified size is less than or equal to current size.

The cause of this error is the PVS database being larger than 20 MB at the time PVS is installed. In this case it was caused by the MODEL database being configured with a fixed size of 500 MB on the target SQL 2008 R2 Server.

Near the end of the install PVS attempts to “increase” the size of the database to 20 MB. I assume this is because it is preparing to insert significant amounts of data (around 20 MB) and proactively increases the database size to avoid the overhead and continually growing the data file. Of course, if they database size is already greater than 20 MB as it was in this case this operation will fail as it is actually attempting to shrink the size of the database.

Our solution was to temporarily reduce the size of the MODEL database while the PVS install was completed. Other workarounds are detailed here in this KB Article from Citrix.

It would be a better model for the installer to first check the size of the database and then increase it only if it is not already 20 MB.

The post PROVISIONING SERVER 5.6 SP1 DATABASE SIZE CAUSES FAILED INSTALL appeared first on eGroup.

http://www.apple.com/icloud/

Any application. Any device. Anywhere.

The post WHY iCloud AND iOS 5 IS A BIGGER DEAL THAN WE REALIZE! appeared first on eGroup.

“Error 1720. A script required for this install to complete could not be run. Custom action VM_AdamLoadVdiSchemaPreReqs script error -2147024894 , : Line 16, Column 1.”

The following update from Microsoft fixed this error:

http://support.microsoft.com/kb/947821

The post ADAM SCHEMA PRE-REQUISITES SCRIPT ERROR – VIEW 4.5 – WINDOWS 2008 R2 appeared first on eGroup.