Archive for the ‘Microsoft Windows 8.1’ Category

How to: Save Windows tiles in Windows 8.1 using RES Workspace Manager 2014

Whitin Windiws 8.1 users are able to add there own Windows tiles on the start screen. Here you can create your own selection of the most used applications and group them together. When you’re usning Windows 8.1 with RES Workspace Manager 2014, you can save this layout. So after logout and login again, the layout is still there.

1.) Open the RES Workspace Manager 2014 Console
2.) Navigate to Compsotion \ User Settings
3.) Create a new setting named: Save Windows Tiles
4.) Add the following two files to be saved
5.) Assign the settings to the right user(s) and Workspace
6.) Login, change your Windows tiles and logout….
7.) Browse to your PersonalSettings folder and see if there is any UPF file

2014-10-01_15h29_48    2014-10-01_16h00_58    2014-10-01_16h02_14

Can’t start Sticky Notes in Windows 8.1 with RES Workspace Manager 2014

Last week I’ve been working on a big VDI environment with RES Workspace Manager 2014, Windows 8 and VMWare Horizon View. Everything looks realy nice and is working realy well!! But I’ve seen one strange thing. One of the applications “Sticky Notes” couldn’t be started from the start menu or Windows tiles. In this blogpost you’ll find a solution for this problem.

1.) Add Sticky Notes to RES Workspace Manager 2014
2.) Open the Properties of the new application and navigate to the second tab “Settings
3.) Scroll down to “Disable file system redirector on 64-bit systems” and Enable this setting
4.) Refresh the User Workspace and start the application again
5.) Sticky Notes can now be used

2014-10-01_09h43_05    2014-10-01_09h44_20    2014-10-01_09h44_27

2014-10-01_09h44_43    2014-10-01_09h44_56    2014-10-01_09h49_04

How to: Set Microsoft Office initials with Active Directory information using RES Workspace Manager 2014

When you’ve installed Microsoft Office in your environment, the first time the user starts one of the Office products, they receive a pop-up box for the initials. Default there are two things the user has to fill in. The username and the initials. The username is the displayname within Active Directory. The initials is the first letter of the username. But, what if you want to fill this field also with some Active Directory information, like the property Initials.

In this environment I’m using RES Workspace Manager 2014, so there’re also possibilities to set some user variables in your session. First I’ve created a new environment variable with a query to read the information from Active Directory.

1.) Open the RES Workspace Manager Console and create a new environment variable. In my example it is Initials
2.) Give the new variable the following value $adinfo(Initials) There’re some more values possible, like firstname, lastname, etc….
3.) Login to your session, in my example a Windows 8.1 VDI desktop and open the command prompt
4.) Type the command set and search for the new variable Initials. It’s the information from the Active Directory
5.) Now return to the RES Workspace Manager Console and create a new User Setting (User Registry)
6.) The values are stored in the following registrykey:
7.) Add this path in the new registry setting and create two new REG_SZ keys
UserInitials with the value %Initials%
with the value %Username%
8.) Configure the Access Control and the Workspace Container
9.) Login again into a new session and start Microsoft Office, for example Word, Excel, Outlook, PowerPoint, etc…
10.) Open the options and take a look at the user initials.

This is a realy powerfull solution to control your users initials. You can choose to apply the User Registry settings once, so the users are able to edit the initials. You can use a User Preference to store this information in a .UPR (User Preference) with RES Workspace Manager.

2014-08-12_15h40_07    2014-08-12_15h40_16    2014-08-12_15h40_47

2014-08-12_15h41_41    2014-08-12_15h43_17    2014-08-12_15h45_09


How to: Directly install from a distribution point during OSD in ConfigMgr 2012 R2

During a OS deployment with ConfigMgr 2012 R2, the WIM file is downloaded locally and than installed on the C: drive of your system. The download proces for the install.wim file takes a while! This post will discribe how to configure the task sequence to directly apply the install.wim from the distribution point.

1.) Open the task sequence and select the step “Apply Operating System”. Navigate to the “Options” tab.
2.) Select “Access content directly from the distribution point” and select “Apply”
3.) Navigate to your Operating System Images and select the properties of the image
4.) Navigate to the “Data Access” tab
5.) Select “Copy the content in this package to a package share on distribution points”
6.) Select “Apply”
7.) The install.wim file will be copied to the SMSPKGE$ folder on your distribution point
8.) Right click on the image and select “Update Distribution Points”
9.) Wait until the content status is “Success”
10.) Start a deployment of a system
11.) The download step is gone now and the image will be installed directly from the distribution point

OSDC_01    OSDC_02    OSDC_03

OSDC_04    OSDC_05    OSDC_06

OSDC_07    OSDC_08    OSDC_09

OSDC_10    OSDC_11    OSDC_12

OSDC_13    OSDC_14    OSDC_15

OSDC_16    OSDC_17    OSDC_18

How to: Install ConfigMgr 2012 R2 hotfix KB2910552 during OSD

A few weeks ago Microsoft has released a update KB2910552 for ConfigMgr 2012 R2. This update fixes a lot of issues, but also speed up the OSD within ConfigMgr 2012 R2. I should highly recommend to install this hotfix in your environment. The hotfix is updating the site system automatically, but the client not. This blogpost will discribe how to install this hotfix during a OS deployment (OSD).

1.) First install the hotfix KKB2910552. The hotfix is vissible in the installation folder of ConfigMgr. In my example E:\Program Files\Microsoft Configuration Manager\hotfix\KB2910552\Client
2.) Copy the content in this folder to your source directory.
In my example \\CM01\Sources\OSD\Hotfix\KB2910552\Client
3.) Add a new package and configure the source location to the right directory.
In my example \\CM01\Sources\OSD\Hotfix\KB2910552\Client
4.) Select “Do not create a program
5.) Distribute the package to your distribution point(s)
6.) Open the task sequence and add a new step “Run Command Line
7.) Select the right package and configure the command line
cmd.exe /c xcopy x64\*.* “C:\Hotfix” /E /H /C /I /Q /Y
This is for x64 systems only! Change x64 to x86 for deployment to x86 systems
8.) In the “Setup Windows and Configuration Manager” step, add the following installation properties
This is for x64 systems only! Change x64 to x86 for deployment to x86 systems
9.) Start the deployment of a x64 system
10.) After the deployment has finished, navigat to the control panel and Configuration Manager
11.) On the general tab you’ll see the new version number 5.00.7958.1104

HF_01    HF_02    HF_03

HF_04    HF_05    HF_06

HF_07    HF_08    HF_09

HF_10    HF_11    HF_12

HF_13    HF_14    HF_15


How to: Configure a “Boot to desktop” group policy for Windows 8.1

New in Windows 8.1 is the “Boot to Desktop” feature, where the user can choose not to boot to the Windows Tiles, but directly to the desktop! That’s a really nice feature if you ask me! How can we centrally configure and manage these feature for all my users or just a group of users? Exactly, through a group policy with User Preferences. It’s a user settings, so you could also use RES Workspace Manager for example.

1.) Navigate to your Group Policy Management Console
2.) Create a new Group Policy and disable the Computer Settings
3.) Open the policy and navigate to User Configuration / Preferences / Windows Settings / Registry
4.) Create a new Registry Item
5.)  Choose for Hive “HKEY_CURRENT_USER” and Navigate in the Key Path to:
6.) The Value name is “OpenAtLogon
6.) Choose the Value type “REG_DWORD
7) The Value data is:
Boots to Desktop = “0″
Boots to Start Menu = “1″
8.) Attach the group policy to a organizational unit(s) and login to your Windows 8.1 machine!

2014-04-16_10h33_44    2014-04-16_10h33_55    2014-04-16_10h35_15

2014-04-16_10h44_40    2014-04-16_10h44_50    2014-04-16_10h45_18

2014-04-16_10h45_31    2014-04-16_10h46_12    2014-04-16_10h46_33

2014-04-16_10h47_03    2014-04-16_10h52_42