Author: siteadmin

Posted on

RES Workspace Manager 2011 Training

The new RES Workspace Manager 2011 training courses are now available.

RES Software have announced the availability of the new RES Workspace Manager 2011 courses (RWMBC-4×0) and the 2 day RES Workspace Manager 2011 upgrade (RWMUC-400) course. Virtual Engine consultants are trained and qualified to deliver this training today either at the partner locations or on customer site.

For more information, please see the training page or contact us.

Posted on

User PWRMENU.INI Preferences

The PWRUSER.INI file stores the user specific settings for their PowerFuse environment. For example, if a user chooses to place certain application shortcuts on the desktop or in the Quick Launch then the application list is stored within this file. That’s all well and good, but what options can I set in PWRUSER.INI file and how do I go about implementing them?

When a user first logs on the default PowerFuse action is to copy the model \PWRMENU directory (under the ‘Configuration Management > PowerLaunch > Directory Maintenance > Home Directory > Settings‘ node in the PowerFuse management console) if it doesn’t already exist to the user’s home directory. This directory is hidden so you might have to change your Windows Explorer settings to see it.

If you wish to set defaults for new users then you can make the required changes in the PWRUSER.INI file directly from the management console. To change the settings for existing users then you will have to implement a Home Directory maintenance task to modify the specific Section, Key and Value settings within the PWRUSER.INI file (you do remember those Windows 3.1 .INI files don’t you!?).

The options for the PWRUSER.INI are not listed in the application help although there is a RES Knowledge Base article, ‘Q200958 INFO: PWRUSER.INI explained‘, that details all the available settings. In case you don’t have a portal login or can’t be bothered to look, here are some of the common settings:

[Preferences]
SmallIcons={Yes/No}
LeftRight={Yes/No}
TimeoutScrnSaver={0/99}
SwapMouse={Yes/No}
Printer={\\server\printershare}
PreviousPrinter={\\server\printershare}
DesktopColor={ColorNumber}
DesktopForeColor={ColorNumber}
HideDescription={Yes/No}
ShowAllOnDesktop={Yes/No}
MessageDefaultPrinter={Yes/No}
NoAppGuard={Yes/No}
OnTop={Yes/No}
LCID={Windows Language Number}
MLS={RES PowerFuse Language Code}

If you’re looking for a particular setting then make the change within PowerPanel and then check the PWRUSER.INI file. I do this all the time for the background colours as they don’t appear to follow any standard RGB scheme that I can decode!

Posted on

HOW TO: Mandatory Profiles

I highly recommend using Mandatory Profiles with PowerFuse in Terminal Services and VDI deployments. There is some information around the Internet detailing how to do this, but none of it appears to be step-by-step and you’ll get various snippets of information from varying sources. Having set this up on numerous occasions and having to piece together the details each time from my notes I thought I’d share them. I’ll cover some PowerFuse specific recommendations and best practices in a future post. Enjoy!

Creating the Mandatory Profile:

  1. Create the mandatory profile on your file server. For example, create the ‘D:\MandatoryProfile’ folder.
  2. Copy the Default User profile directory to the ‘D:\MandatoryProfile’ folder.
  3. Rename the ‘Default User’ folder to ‘Mandatory’ (or whatever you wish).
  4. Rename the D:\MandatoryProfile\Mandatory\NTUSER.DAT file to NTUSER.MAN.
  5. Remove NTFS permission inheritance and copy the existing permissions.
  6. Remove all named ACEs for all non-“Well Known Groups” and users.
  7. Add ‘Authenticated Users’ with Read and Execute permissions.
  8. Change the Owner of the directory (and sub-directories/files) to the local ‘Administrators’ group.
  9. Share the ‘D:\MandatoryProfile’ folder as ‘Mandatory’.
  10. Add ‘Authenticated Users’ with Read permissions to the share permissions

Modifying the Profile:

  1. Delete the NTUSER.LOG file and any other files/shortcuts that you don’t want available to the users from the ‘D:\MandatoryProfile\Manadatory’ folder.
  2. Change the registry permissions in the HKCU registry hive:
    1. Open REGEDIT.
    2. Highlight the HKEY_USERS hive.
    3. Select ‘File > Load Hive‘.
    4. Browse to the ‘D:\MandatoryProfile\Mandatory\NTUSER.MAN‘ file.
    5. Enter a name for the hive. This is only a place holder whilst the HKCU hive is loaded and can be named anything you like, i.e. ‘MAND’.
    6. Edit the permissions (Right click > Permissions) on the loaded hive and;
      1. Remove any non-“Well Known Groups” or individual users.
      2. Add the local ‘Users’ group with Full Control.
    7. Make any specific registry changes required here, for example, disabling the default Windows Startup sound.
    8. Unload the registry hive by highlighting the ‘MAND’ key and selecting ‘File > Unload Hive‘ from the menu. If you don’t unload the registry hive users will not be able to load the mandatory profile and receive errors at log on.
  3. Add additional files and shortcuts that you want available to the users, e.g. desktop shortcuts.

Assign the Mandatory Profile to users:

  1. To assign the Mandatory Profile to Terminal Services users, specify the users ‘Profile Path‘ setting as ‘\\SERVER\Mandatory\Mandatory‘ on the ‘Terminal Services Profile‘ tab of their AD account(s).
  2. To assign the Mandatory Profile to desktop and laptop users, specify the users ‘Profile Path‘ setting as ‘\\SERVER\Mandatory\Mandatory‘ on the ‘Profile‘ tab of their AD account(s).
  3. To assign the Mandatory Profile to VDI users, assign the profile as per the ‘desktop and laptops’ option above.

Virtual Engine Limited
450 Brook Drive, Green Park, Reading RG2 6UU