A press release from Immidio landed in by inbox today – Flex Profiles, formerly by Login Consultants, has been updated to version 6. It comes as a free Express version and from what I can tell, you can pay for support.

Immidio announces the launch of Immidio Flex Profiles 6.0, the successor of the popular Login Consultants freeware tool. Immidio Flex Profiles gives administrators full control over Windows user profiles on workstations, remote desktops and virtualized applications. Immidio Response provides tailored product support programs based on the size and complexity of the IT environment.

I must admit that I haven’t looked at version 6, but I have used earlier versions quite extensively in the past in Terminal Server environments, and it was always a great way to manage user profiles.

Flex Profiles 6 is available is post from stealthpuppy.com. Except as noted otherwise, this work is ©2005-2010 Aaron Parker and is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.

At some point in your migration from Windows XP to Windows Vista you’ll no doubt be looking to manage which Control Panel applets are available to users. Controlling access to applets is no different than earlier version of Windows, but given that there are approximately 48 default applets in Windows Vista compared to 29 in Windows XP, more consideration will need to be given to those which you make available.

There’s a good chance that list will be different for everyone, but here’s my approach: Hiding Control Panel applets is not a replacement for ensuring users are not logging into their workstations with administrative access. Without administrative access, users cannot make system wide changes. Restrict applets too much and you can make support difficult.

I consider the task of restricting the available applets as a means of de-cluttering the interface, not ‘locking the system down’.

Here’s what Control Panel applets I would consider to be relevant to most users in a Windows XP environment:

A couple of these may not be completely necessary, but they give users enough access to manage their environment to suit the way they work. Note that there’s nothing in these applets (yes, including Network Connections) that lets standard users change system settings. There are also many Group Policy settings that allow you to be fairly granular for settings within these applets.

This is what I’m looking at providing for users in Windows Vista:

As you can see there’s many more icons, but Vista does provide many more features. There are a few applets here that you may wonder why I’ve not hidden them:

• Network and Sharing Center: especially useful to laptop users for providing connectivity information
• Problem Reports and Solutions: Vista does a good job of providing solutions for device and software compatibility issues
• System: Information list here is useful for support personnel, hard to see this info if this applet is unavailable
• User Accounts: this will allow users to change their user picture

Here’s a short list of recommendations when configuring Group Policy for the Control Panel:

• Leave the standard Control Panel view as the default – don’t be tempted to force Classic view. The default view in Windows Vista is less cluttered and search makes finding the right option easier.
• Provide the complete list of Control Panel applets across all device types in a GPO on the user’s OU using the Show only specified Control Panel items policy
• Remove additional applets from the previous list for special case machines (e.g. Terminal Server) in a loop-back policy using the Hide specified Control Panel items policy
• Using applet names in these policies provides more granular access than using the .CPL filenames (plus they’re easier to read)

There are also a couple of other settings that remove options that users don’t need to see:

• User Configuration / Policies / Administrative Templates / Windows Components / Windows Explorer / Remove Hardware tab
• User Configuration / Policies / Administrative Templates / Control Panel / Regional and Language Options / Hide Regional and Language Options administrative options

And finally, here’s what Control Panel under Windows 2008 Terminal Server might look like:

So, what do you think – am I off my tree for giving users so many options? Or can I get some support for the ‘enabling users’ camp?

Managing Control Panel in Windows Vista is post from stealthpuppy.com. Except as noted otherwise, this work is ©2005-2010 Aaron Parker and is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.

Got both Visio Viewer 2007 and Visio 2007 on the same machine but want to set Visio Viewer as the default for some users? Here’s what you’ll need to do.

With Visio 2007 and Visio Viewer on the same machine, Visio will the default application for .VSD files, so we need change the default application per user, taking advantage of the HKCU\Software\Classes key.

The following registry entries will set Visio Viewer as the default. You can deploy this as a .REG file via a logon script or better yet, use a workspace management tool such as Group Policy Preferences, AppSense Environment Manager or RES PowerFuse.

[quickcode:noclick]Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Classes\.vsd]
@=”VisioViewer.Viewer”
“Content Type”=”application/vnd.ms-visio.viewer”

[HKEY_CURRENT_USER\Software\Classes\.vsd\shellex]

[HKEY_CURRENT_USER\Software\Classes\.vsd\shellex\{8895b1c6-b41f-4c1c-a562-0d564250836f}]
@=”{21E17C2F-AD3A-4b89-841F-09CFE02D16B7}”

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer]
@=”Microsoft Visio Document”

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\CLSID]
@=”{279D6C9A-652E-4833-BEFC-312CA8887857}”

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\CurVer]
@=”VisioViewer.Viewer.1″

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\DefaultIcon]
@=”\”C:\\Program Files\\Microsoft Office\\Office12\\VVIEWER.DLL\”,-2″

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell]
@=”"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open]
@=”Open”

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open\command]
@=”\”C:\\Program Files\\Internet Explorer\\iexplore.exe\” -nohome”

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open\ddeexec]
@=”\”file:%1\”,,-1,,,,,”

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open\ddeexec\Application]
@=”IExplore”

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open\ddeexec\Topic]
@=”WWW_OpenURL”

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer.1]
@=”Microsoft Visio Document”

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer.1\CLSID]
@=”{279D6C9A-652E-4833-BEFC-312CA8887857}”
[/quickcode]

Although Visio Viewer is installed as a component of Office 2007, you can download a separate installer here and SP1 here.

Setting Visio Viewer As Default is post from stealthpuppy.com. Except as noted otherwise, this work is ©2005-2010 Aaron Parker and is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.

As you’re probably aware, because all the major blogs have covered it already, Citrix has purchased sepagoProfile from sepago with an agreement for sepago to continue development over the next 18 months. The product will become Citrix User Profile Manager.

I’m a fan of sepagoProfile because it’s very simple and Group Policy based, which is a much better approach than one of the other major user profile management solutions that I’ve been working with in the past year. Teaming this with Group Policy Preferences gives you almost everything you’ll need to manage the user workspace.

If you haven’t seen sepagoProfile yet, I recommend downloading a copy from My Citrix and giving it a spin.

Citrix Enters The Profile Management Space is post from stealthpuppy.com. Except as noted otherwise, this work is ©2005-2010 Aaron Parker and is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.