|
|
|
15. How do you resolve slowness on the Stratusphere™ Hub when running reports and navigating the UI?
Here is the process to upgrade a Stratusphere™ Hub to the latest version:
NOTE: If using 4.6.1 or prior versions, please contact Support to request help with the upgrade process.
Stratusphere™ appliances are designed to run on VMware ESX/ESXi and Citrix XenServer platforms. Liquidware Labs does not test running these appliances on VMware Workstation or VMware Server. However, if users want to run the appliances on a VMware Workstation or VMware Server platform, Liquidware Labs recommends using VMware Converter 4.x to convert the OVF files into the VMware target platform of choice.
Stratusphere™ appliances are designed to run on Citrix XenServer platforms. Liquidware Labs provides the XVA files for XenServer Virtual Appliance import capability. These files can be directly imported from with XenCenter to import the Stratusphere™ virtual appliances, connected to the appropriate networks and powered ON. Stratusphere™ console access will then be available to configure the appliance. Please refer to the Stratusphere™ Quick Start Guides on the Liquidware Labs Download/Support pages for additional information.
Stratusphere™ Hub virtual appliance is compatible with Microsoft Hyper-V. Liquidware Labs provides a zip file that contains all files needed to import it within Microsoft Hyper-V Manager. Once imported, the virtual appliance can be configured as any other virtual machine such as for memory, hard disks, and connecting the NIC to the appropriate networks. It can then be powered ON. The Stratusphere™ console access as well as the Network Configuration web page will then be available to configure the appliance. Please refer to the Stratusphere™ Quick Start Guides on the Liquidware Labs Download/Support pages for additional information.
Stratusphere™ does support an external database configuration. However, this database is embedded inside a Stratusphere™ Database Appliance. This configuration should be used when there are more than 1,000 CID Keys reporting to a single Stratusphere™ Hub. It should be used for better performance and quicker callback frequencies from the CID Keys. The Stratusphere™ Database Appliance is available for download as an OVF from Liquidware Labs download page. Please refer to the Stratusphere™ Quick Start Guides on the Liquidware Labs Download/Support pages for additional information.
Storage capacity on the Stratusphere™ Hub can be increased by adding a new hard disk to the appliance. The Stratusphere™ Hub does not support expanding an existing data disk. To add a new hard disk, please shut down the Stratusphere™ Hub appliance using the 'Shut Down Guest' option within the VI/vSphere Client. Edit the settings of the Stratusphere™ Hub and add a larger disk to the appliance. Please refer to the Sizing Guidelines on the Customer Support page of Liquidware Labs. After adding a new hard disk, power ON the Hub and log into the console using ssconsole/sspasword credentials. Now execute the "show disk" command. Any new uninitialized disk will be displayed by this command. If a third hard disk was added to the Stratusphere™ Hub this third disk will be displayed as "sdc". Execute "add disk sdc" command. This command will stop relevant services on the Stratusphere™ Hub, initialize the newly added third disk, format it, copy the older data files from the second disk partition to the new disk, and finally start the relevant services again. While this command runs, a lot of messages will be displayed on the console eventually ending with "Done" if successful. If there is an error, please run the command again. If the errors persist please contact Support.
Here is the process to add storage to a Stratusphere™ Hub on XenServer:
Here is the process to add storage to a Stratusphere™ Hub on Microsoft Hyper-V:
This process is applicable to Stratusphere™ Database Appliance running on VMware ESX, Citrix XenServer, and Microsoft Hyper-V. Here is the process to add storage to a Stratusphere™ Database Appliance:
Log in under Administration section of the Web UI using the default credentials ssadmin/sspassword. Navigate to the Hub Administration > Connector ID Keys > Connector ID Key Properties tab. Change the Callback Frequency to 36hours and save the settings by clicking on the "Apply Changes To" button. Then navigate to Data Retention > Auto-Delete Settings tab. Change the Auto-Delete audit data settings to 1day. After a period of 24hours, check the Data Retention > Status tab to check the disk size of the data on the appliance. Once the data has been purged, you can reset the original settings for the Callback Frequency and Auto-Delete Settings.
Liquidware Labs recommends extreme caution when changing the ssadmin password. If the new password is lost or forgotten there is no way to recover the ssadmin account resulting in loss of access to the Stratusphere™ Hub UI. Liquidware Labs recommends creating a new user with the desired password before changing the ssadmin password. To create a new user log into the Stratusphere™ Administration section of the UI. Navigate to the Inventory > Users tab and click on the "New" button to create a new user. Enter the user name, set the desired password for account, change the role to "Administrator", and select "Yes" to enable the user. Click on "Create User" button to create this new user. Log out of the UI and test the new user and credentials and make sure you have access to the UI. Once you have verified access, select "ssadmin" user from the Inventory > Users tab and click on "Edit" button. Disable the "ssadmin" user by selecting the "No" option. Then click on "Save changes" button. The ssadmin user will no longer be able to access the UI.
As of version 4.8.0 the Network Configuration webpage is only available until the Stratusphere™ Hub is not configured. Once configured, the page is no longer accessible. If any configuration changes need to be applied to the Stratusphere™ Hub then it can be configured via the Stratusphere™ Console. Log in to the console using the default 'ssconsole/sspassword' credentials. Enter a '?' to get a complete listing of all the commands available on the console. The most frequently used commands are 'show management', 'show system', 'show dns', and 'show ntp'. These commands display individual commands with the current values configured. Execute these individual commands to change values and reconfigure the appliance. After making the required changes, execute a 'write' command to save all the changes. Refer to the Reference Guide for a complete list of all Command Line Interface API.
Yes. Stratusphere™ can import user and user group information from Active Directory or any LDAP compliant name store. Log in to the Administration section of the Stratusphere™ UI using ssadmin/sspassword credentials. Navigate to the Hub Administration > User Directories tab. Create a new directory, configure parameters to the domain and then save the directory. You can now manually import the user and group information or schedule it to import on a regular basis. NOTE: Liquidware Labs would like to caution users to first find out how many groups exist in their Active Directory prior to performing an import. It is our experience that in most organizations there are hundred times more groups than there are users thus defeating the purpose of trying to manage through user groups. Also, the process of importing an LDAP compliant name store is irreversible because the existing users are then linked to their DNs imported from the name store and the name store is then considered the master list of users. The process is irreversible because deleting a Active Directory will result in deletion of all user information as well.
Yes. Stratusphere™ can import user group membership information from CSV files. Log in to the Administration section of the Stratusphere™ UI using ssadmin/sspassword credentials. Navigate to the Hub Administration > User Directories tab. Select the Local Directory that already exists. Navigate to the "Import From CSV File" tab and click on the links below the fields to get the format of the files that contain user information and group information. The square brackets are not required.
Always upgrade the Stratusphere™ Hub to the latest version available. Once upgraded to the latest version you can allocate 2 to 4 vCPUs to the Stratusphere™ Hub. You can also allocate up to 8GB of Memory to the Stratusphere™ Hub. The Hub should also be installed on an ESX or XenServer host with plenty of CPU and Memory resources available. The data disk of the Stratusphere™ Hub should be on a data store with lower number of VMs to maximize IO throughput. If there are too many scheduled reports running, try reducing the number of reports that are automatically scheduled to run. If there are 1000+ CID Keys calling back you could consider using the Stratusphere™ 4.8 Database appliance to gain higher performance.
The standard Stratusphere™ deliverable is called the Assessment Findings report. You can kick off this report by navigating to the Assessment > Summary tab and clicking on the "Generate Summary Report" button. On selecting your time period you can navigate over to the Assessment > Reports tab to view the Report Archive. Depending on the time period selected the report could take a significant amount of time to finish. A 45page summary PowerPoint based report with general findings and assessment candidates will be generated.
The SAN related reports rely on data that is imported from VMware Virtual Center. If the Inspector or Report is empty, please ensure that the VM Directories have been configured within Stratusphere™. Log into the Administration section of the Stratusphere™ UI and navigate to the Hub Administration > VM Directories tab. Create a new VM Directory and configure it to connect to your Virtual Center. Once configured you can import data manually or schedule it to automatically import data on a scheduled basis.
The HOST related reports rely on data that is imported from VMware Virtual Center. If the Inspector or Report is empty, please ensure that the VM Directories have been configured within Stratusphere™. Log into the Administration section of the Stratusphere™ UI and navigate to the Hub Administration > VM Directories tab. Create a new VM Directory and configure it to connect to your Virtual Center. Once configured you can import data manually or schedule it to automatically import data on a scheduled basis.
To fix the certificate errors you need to place a signed certificate in the hub.
Note: ProfileUnity runs on a different port from Stratusphere. ProfileUnity runs on 8443. Stratusphere™ runs on 443.
OR
Note: Access the UI from the
web browser and see if it works without warnings. If it fails, replace
/var/empty/backend/.keystore with /var/empty/backend/.keystore.
If the database service has crashed or too busy you can get this error, so first try to restart services and wait several minutes. If that didn't work then log in as friend and do a "df" command. If you see /var/lib/pgsql on two partitions you may have an issue that requires you to contact Liquidware Labs support.
This error is generally seen when the database service cannot start or connect to the database. It is mostly observed after adding a new disk to the Stratusphere™ Hub appliance. The "add disk <sdc>" command had issues if it was adding a new disk for a Hub that was under load. Please contact Support to resolve this issue.
If you have gone through the "add disk sdc" command and then are encountering database connection issues or the data seems to have disappeared from the UI then do the following:
If the Stratusphere™ appliance was collecting data for a few days, this copy process may take a while to complete. Please be patient.
Liquidware Labs recommends Thick Provisioning the data disks on the Stratusphere™ Hub. Liquidware Labs does not test the appliances with Thin Provisioned disks.
As of version 4.8.0, email server can only be configured via the Stratusphere™ Hub Console command line. Here are the instructions:
This command shows you all the different settings under the system
This command sets the mail relay server ip or dns.
The server can be MS Exchange or a Lotus Notes Server or any other mail relay server. The server must have policies to allow it to accept/ receive inbounding mail from the Stratusphere™ Hub's IP Address.
This command saves the settings
Use this command to verify that the settings got updated
As of version 4.8, the Stratusphere™ UI does not provide an easy way to export all data from one Hub to be imported into another Hub. If it is absolutely necessary, Liquidware Labs Customer Support could potentially export/dump the database from Hub and restore to the other Hub. This is a highly manual and time consuming procedure. This capability is part of the roadmap and will be available as a feature in a future version.
The Advanced CID Key can capture all the information that a Standard CID Key can collect – so from a metrics collection perspective there is no difference in capabilities. However, the Advanced CID Key also has a network component that gets installed into the network stack on the desktop. It implements our patented piece of software that embeds the identity of the user and machine into every network connection (SYN) packet that is initiated through the machine it's installed on. It is rarely or almost never used for assessments on physical desktops and is generally used in monitoring & diagnostic environments to track the user/machine's activity through the network in conjunction with the Network Station virtual appliance. We strongly recommend using the Standard version of the CID Key because it can be installed and uninstalled any number of times with no conflicts. Since the Advanced CID Key has a network components it might ask for a reboot on installation and could potentially cause conflicts with physical desktops/laptops that might have other software components in the network stack including VPNs, AVs, and firewalls. It should be tested in a lab scenario prior to pushing it out to your desktop population.
Here are a few reasons why the CID Keys are not sending data back:
The CID Key on Windows® has three services that run under the SYSTEM context in the background. To stop these services you can go into the Control Panel > Administrator Tools > Services applet and stop the Liquidware Labs services. You can also open the command prompt and execute the following commands in the order listed below:
Note: Please make sure that you DO NOT change the order because of the process dependency. If you need to restart services, please do so in the reverse order.
Yes. There are two ways you can achieve this. The first option involves uninstalling the existing CID Key and then reinstalling the CID Key with the installer from the new Hub. The second option involves, stopping all CID Key services on the desktop, editing the registry settings to point to the new Stratusphere™ Hub's address, and the restarting the CID Key services. Both these options can be carried out across multiple desktops using SMS or any scripting capability you may be familiar with. The second option requires the following text to be pasted into a TXT file that can be renamed as CID_HubAddress.REG. Replace the IP Address with the DNS Address or the IP Address of the new Stratusphere™ Hub. The contents of the .REG file are:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\
"hubAddress"="new.hub.ip.dns"
[HKEY_LOCAL_MACHINE\SOFTWARE\
"hubAddress"="new.hub.ip.dns"
Once the file is created, here are the steps to make this change:
No. As of Stratusphere™ 4.8.0 we do not have the ability to transfer data collected by a CID Key for a machine to a different Hub.
The agent collects data through several means. Many metrics are gathered from WMI, but others are based on proprietary algorithms.
Communication between the Connector ID and Hub is over TCP/5501. Each sample collected is 30 Kb of data. Communication between Network Station and Hub is over TCP/5502. There is no set data size here because it varies according to how much network traffic occurs within the target network. Your browser based user interface connects over TCP 443.
You should see: vmware-guestd is running
The appliance *will* need an additional disk now. This isn't an issue for new installs as we've increased the disk size there. For new install this isn't an issue as they've already added a new data disk as the default one is too small. What we're trying to do in the 4.6.2 upgrade is re-use the *original* database space for more swap so the database needs to be on a different disk. So, if it's a default appliance, you'll need to add a disk and then go through the 'add disk' steps in the console to move the database to the new disk. Once that has been done...
/opt/tnt/var should be on /dev/sdb2:
Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdb2 497861 93372 378785 20% /opt/tnt/var
Filesystem 1K-blocks Used Available Use% Mounted on - 1947720 216 1947504 1% /dev
SwapTotal: 1534196 kB
(This is from a new install so the number for an upgrade might be a little different).
Known Issues
Upgrade will fail if the swap space is not enough. See upgrade notes above
Once upgraded to 4.6.3, there is a patch for report performance that will need to be applied to 4.6.3. Please see instruction for 4.6.3 patch.
No, never.
The biggest advantage for the standalone version is you don't need virtual infrastructure, and stand alone is very light weight. Standalone requires a machine, whereas the hub is a virtual appliance that runs on Linux so it doesn't require extra Windows licensing. With the virtual appliance no physical machine is required, and the appliance is easier to upgrade.
Running the stand-alone version of ProfileUnity
Running the Stratusphere™ Hub
If you have multiple INI files in the Profile Unity folder:
Prior to version 4.7 multiple INI files would break the rsynch process which drives our "Synch Option" on Folder Re-direction as well our ability to deliver local-cached mode ThinApps to a desktop. In addition, there have been reports of ThinApp delivery issues when multiple ini files are in place prior to 4.7.1. This is fixed in the 4.7.1 release.
It should be noted that if there are multiple ini files and the user is entitled to execute them, they are executed in alphabetical order except for default.ini. Default is executed first and then all the other files in alphabetical order.
Multiple ini files can be useful in larger environments or in any environment where there are large groups of users that require their ProfileUnity configuration to have a large amount of differences (e.g. different portability and different save paths, different provisioning tasks altogether) or in environments where there could be multiple admins making configurations.
Filter Management gives you the ability to make finer grain adjustments within a singular ini file. For example, all users have their portability settings saved to their home drive, but we want to provision different printers or drives for different departments. In those cases, filter management may be the best approach.
Portability Rule Set defines the possible things that can be harvested, backed-up and restored session to session.
Folder-Redirection is the concept of changing the User's registry setting of one or more shell folder location from the default location in the local file system to a network share or path.
Portability Settings have two components, a registry setting and a file system setting. The registry setting defined a Merge, Replace or Exclude function on a Tree, Key or Value in the HKEY Current User Registry hive. All paths in this section of a Rule Set are relative that hive.
The Filesystem component defines a Merge Replace or Exclude on a file, directory or set of files (using wildcards) relative to a starting directory (e.g. Application Data, User Profile, system drive, etc.) the path specified here is relative to the folder you select.
There are multiple items that can affect login and logoff times. Chief among these is related to the portability rule sets that are enacted and the amount of data they are harvesting, backing up and restoring. Examining the size of the 7z archives that are created is one way to see if these files are large and if a "tuning" of the rule set is required.
For example, the default application
data rule set when invoked merges the entirety of the user's application
data folder with a couple of exceptions. There are many different
non-essential files and directories in this folder (sun\java\deploymentsystem\
In addition to portability rule sets, provisioning tasks such as the additions of excessive & multiple printers, or delivery of many and multiple provisioning tasks can also impact the loading times for users.
Open up regedit on your XenApp
server and browse to the following location: HKey_Local_Machine\Software\
The PDF file is the more simple and readable format.
The ntuser.dat file cannot be compressed and zipped by Profile Unity due to the fact that it is locked by the OS. In essence, the portability rule sets capture the information that is contained in the ntuser.dat file, so capturing that file is unnecessary.
In the console you can find the version by logging in as
User: ssconsole
Password: sspassword
Then use the "show version" command to see the version of the hub.
Turn on portability for HKEY_CURRENT_USER\Software\
HKEY_CURRENT_USER\Software\
and
%userprofile%\appdata\roaming\
This is the same as the default passwords rule set.
Yes. To fix the issue with published applications not running, open up regedit on your XenApp server and browse to the following location:
HKEY_LOCAL_MACHINE\SOFTWARE\
For the Userinit value you will
need to replace C:\Program Files\ProfileUnity\userinit.
Note: For 4.7.1 and later this should be automatic and ctxinit.exe is used instead of userinit.exe.
ProfileUnity includes a filter that is based on LAN or WAN connections.
ProfileUnity is tested with ThinReg 4.5 and later.
Add the user to the profile unity group and have the user log in and out as soon as the .ini applies to him.
| Administrators | Full | This folder, subfolders and files |
| SYSTEM | Full | This folder, subfolders and files |
| Authenticated Users | Modify | This folder only |
| CREATOR/OWNER | Modify | Subfolders and files only |
| HelpDesk Group | Modify | This folder, subfolders and files |
These settings will allow ProfileUnity to create subfolders for each user and these created users will be accessible only by the intended user.
Note: The "HelpDesk" entry should be replaced by the group containing your helpdesk staff. This will allow your helpdesk to modify the user profile data for all users.
Your desktop icons are normally
saved using the Windows Explorer portability ruleset in ProfileUnity.
However, if you have this setting enabled, "Arrange Icons By–>Align
Icons to Grid", enabled in on the Windows desktop then this will cause
icons to be auto-arranged to the left side of the screen at logon and
logoff time. In order to have ProfileUnity manage icon placement
you will need to turn this option off. This can be done on the
desktop by right clicking on the desktop and unchecking the checkbox
by "Arrange Icons By–>Align Icons to Grid" or you may change the
value in the registry at: HKEY_CURRENT_USER\Software\
Set Auto Arrange off, Align to
Grid off:
"FFlags"=dword: 0x00000220
Enable then disable the timestamp check option in the group policy settings.
