Skip to content

Get Ready Now To Deploy Internet Explorer 8

28-Aug-08

Unless you’re hell bent on deploying Firefox in your corporate environment (and managing it with Group Policy), here are some reasons why you should plan for Internet Explorer 8 now and deploy it when the final version is released:

  • Compatibility View mode will ensure those internal web applications don’t break. Intranet sites are displayed Compatibility View mode by default.

CompatibilityViewSettings

  • It’s also really simple for users to enable Compatibility View with the Compatibility View button CompatibilityViewButton
  • There are more than 100 new Group Policy settings added for Internet Explorer 8
  • DEP is turned on by default for Internet Explorer 8. DEP helps to improve security for ActiveX controls
  • You can enforce the SmartScreen Filter to block access to malicious sites and downloads. Great for those laptop users accessing the Internet outside of your network
  • Loosely-Coupled IE and Automatic Crash Recovery will help make happy users
  • Developer tools are included to help your devs work with their web sites
  • Internet Explorer 8 can be slipstreamed into your Windows XP/2003 or Windows Vista/2008 images for faster deployment

For complete information on IE 8 for the enterprise check out this document: Windows Internet Explorer 8 Beta 2: Technology Overview for Enterprise and IT Pros. You might also be interested in the Windows Internet Explorer 8 Beta 2 Release Notes as well as the Internet Explorer Administration Kit 8 Beta (direct link to the Internet Explorer Administration Kit 8 installer).

Update: Mary-Jo Foley has more details on IE 8 features for the Enterprise.

My Product Code Is Bigger Than Yours..

28-Aug-08

I thought 25 character product keys where a pain in the proverbial, but this one takes the cake. I won’t tell you which application this authorisation code is for, but it’s a whopping 93 characters long..

AF3KALKNHEU777AGRBZ672EKB6I53P6VRND7PLPHCVFWGNSDNB4WYK55HE7YX2TWTLU78M8KLYZ4QERNT3K56OH6TSAXC

(I’ve changed the code slightly to protect the guilty).

WSUS Update for Server Manager in Windows 2008

27-Aug-08

Microsoft have made available an update for Windows Server 2008 that integrates the WSUS 3.0 console into Server Manager.

By default, Windows Server 2008 includes several server roles. Server Manager enables integration of additional roles and features that are available from the Microsoft Download Center and from Windows Update Web sites as optional updates to Windows Server 2008. One role that is available as an update is Windows Server Update Services (WSUS) 3.0 with Service Pack 1 (SP1). This update for Server Manager in Windows Server 2008 fully integrates WSUS 3.0 SP1 into Server Manager. This update lets you use the Server Manager snap-in and wizards to install, configure, and manage WSUS 3.0 SP1.

ServerManager

You can read about the update via the knowledge base article and then download the update for Windows Server 2008 32-bit or Windows Server 2008 64-bit.

Managing Control Panel in Windows Vista

19-Aug-08

In This Series: Migrating from XP to Vista

  1. Customise the Windows Vista Default User Profile
  2. Managing Control Panel in Windows Vista

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:

WindowsXPControlPanel

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:

Control Panel Home

WindowsVistaControlPanel

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:

Windows2008ControlPanel

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?