Reset file ownership based off parent folder name

For anyone who does quota management, I’m sure you’ve run into issues where the Administrator account is incorrectly the owner of 1,000,000 files located in various users’ folders. Of course, you can go to each user’s folder and manually reset it to the correct owner. But, why?

If your user folders are set up in this format:


You can simply use FOR loop along with the ICACLS command to reset the ownership of all of the files (among other things).

Here’s the snippet:

@echo off
SET D= D:\users
FOR /F %%A IN ('DIR %D% /AD /B') DO icacls %D%\%%A /setowner %%A /t /c /q

Just put it in a .bat file and you’re good to go!

For more information, check out the documentation on ICACLS at

Stop using SQL Server path’s work with a SQL Alias

A lot of times i run into customers how started out with one SQL server and run in to problems when these servers have to be upgrade or the databases needs to be migrated to different SQL servers of clusters because of expansion or recourses. Let’s say you have an application that has a specified database connection that I either can’t or don’t want to change. However, I need to move the database to a new server. How can I do this easily without breaking other things that maybe using this connection and/or database?

By using an alias! We can keep the application configuration the same, but tell the operating system to look somewhere else for the database. Another plus is that once an alias is created, it is set at the operating system level. That means if we have two applications which connect to MySQLServer on that computer, once the alias is created, both will be re-pointed based on the alias. You can create an alias using one of two utilities:

  1. SQL Server Configuration Manager
  2. SQL Server Client Network Utility

SQL Server Configuration Manager

Let’s start by looking at how to do it using SQL Server Configuration Manager. In the left pane of SQL Server Configuration Manager, if you expand the SQL Native Client Configuration folder, there is a subfolder called Aliases (see Figure 1). If we click on this subfolder, we’ll see any aliases that have been defined for the system shown in the right pane. In most cases, there won’t be any defined. To create a new alias, right-click on Aliases and choose New Alias… from the pop-up menu.

Figure 1:


A dialog window comes up (Figure 2) which allows us to specify our new alias. In the Alias Name property, you specify the name the application uses. For instance, if it connects to a SQL Server called MyOldServer, that’s what you enter in here. You can also enter an alias that appears to point to a named instance, such as MyOldServer\MyInstance. You can then specify the server where the database really is, to include configuring the protocol, the server name, and the port. Clicking the OK button will create the alias. In the case of Figure 2, I’m creating an alias called MyOldServer which points to my local server’s default instance.

Figure 2:


You should now see the new alias listed in the right pane (Figure 3).

Figure 3:



The next step is to test the connection. You can do so quickly by either creating and testing a Data Source Name (DSN), or if you have the SQL Server client tools installed, by using SQL Server Management Studio (SSMS). I’ll do so using SSMS. Figure 4 shows the dialog window to open a new connection to a database engine. For Server name:, enter in the alias you specified. In the example we called the alias OldServerName, so that’s what we’ll use here.

Figure 4:


If the alias is pointed correctly to the new location, a successful connection should be established. In SSMS, I was opening a new connection for Object Explorer. Figure 5 shows that the connection was successfully made using the alias. Note that as far as SSMS is concerned, the server name is the alias.

Figure 5:


SQL Server Client Network Utility

If you haven’t installed the SQL Server 2005/2008 client tools, you can still create an alias using the SQL Server Client Network Utility. This has come installed automatically on every operating system from Windows 2000 on. To bring up the utility, click on Start, then Run, and run cliconfg.exe. To view or create aliases, click on the Alias tab (Figure 6). As you can see from Figure 6, aliases created by SQL Server Configuration Manager can be seen by the SQL Server Client Network Utility. The reverse is also true.

Figure 6:



To create a new alias, click on the Add… button. This will bring up a new dialog window where you can specify your alias (Figure 7). Just as with SQL Server Configuration Manager, the Server alias is what the application will attempt to connect to. You can specify where that alias points to by specifying the network library, the real server name, and any additional configuration parameters. In Figure 7 I’m creating a new alias called MyOldServer2 that also points to the default instance of my local server.

Figure 7:



Click the OK button to create the new Alias. In order for the alias to actually be created, however, you must click the OK button for the SQL Server Client Network Utility, which will create the alias as it closes.


Now that you know how to create an alias to a SQL Server instance look at this option instead of having hard SQL connections to server and run into problems when you want to reinstall or rename your servers. Also some application do not give you the ability to connect to a named instance, so this is another way of connecting without having to use the a default instance.

The Microsoft Virtual Machine Converter 2.0

Microsoft Virtual Machine Converter (MVMC) 2.0, a supported, freely available solution for converting VMware-based virtual machines and virtual disks to Hyper-V-based virtual machines and virtual hard disks (VHDs).

MVMC can be deployed with minimal dependencies. Because MVMC provides native support for Windows PowerShell®, it enables scripting and integration with data center automation workflows such as those authored and run within Microsoft System Center Orchestrator 2012 R2. It can also be invoked through the Windows PowerShell® command-line interface. The solution is simple to download, install, and use. In addition to the Windows PowerShell capability, MVMC provides a wizard-driven GUI to facilitate virtual machine conversion.

MVMC 2.0Migration-of-a-VM-with-MVMC-2.0_thumb

With the release, you will be able to access many updated features including:

  • Added support for vCenter & ESX(i) 5.5
  • VMware virtual hardware version 4 – 10 support
  • Linux Guest OS migration support including CentOS, Debian, Oracle, Red Hat Enterprise, SuSE enterprise and Ubuntu.

Microsoft has also added two great new features:

  • On-Premises VM to Azure VM conversion: You can now migrate your VMware virtual machines straight to Azure. Ease your migration process and take advantage of Microsoft’s cloud infrastructure with a simple wizard driven experience.
  • PowerShell interface for scripting and automation support: Automate your migration via workflow tools including System Center Orchestrator and more. Hook MVMC 2.0 into greater processes including candidate identification and migration activities.

At this time, Microsoft is also announcing the expected availability of MVMC 3.0 in fall of 2014. In that release we will be providing physical to virtual (P2V) machine conversion for supported versions of Windows.

For more information about the MVMC 2.0 solution including how to download, make sure you visit here.


With Windows Server 2012 R2 Hyper-V and System Center 2012 R2, Microsoft has a solution to enable customers to virtualize their key, mission critical workloads and realize significant savings compared to VMware. Hyper-V enables customers to run their largest workloads. It offers massive host, VM and cluster scalability. It provides powerful storage, networking, and automation features that enterprises and service providers demand. With a number of supported tools, you have many options available to test and continue your migration to Hyper-V.

XenApp & XenDesktop 7.5

XenApp & XenDesktop 7.5

Citrix heeft enkele weken geleden nieuwe releases uitgebracht van XenDesktop en XenApp. Dus niet alleen een nieuwe versie van XenDesktop maar ook (terug van weg geweest) een nieuwe versie van XenApp versie 7.5. Dit is verrassend gezien het feit dat met de komst van XenDesktop 7 XenApp een onderdeel was geworden van het XenDesktop product als zijnde XenDesktop App edition. Nu dus toch weer een nieuwe release van XenApp als product. XenApp 7.5 is net als we al gezien hebben in de XenDesktop 7.x versie nu ook gebaseerd op de nieuwe FlexCast Management Architecture (FMA). Deze architectuur kennen wel al vanuit eerdere XenDesktop 7.x. versies. IMA heeft daarmee zijn langste tijd gehad en gaan we waarschijnlijk ook niet meer terug zien. FMA heeft onder andere als voordeel dat het minder architectuur nodig heeft en het met een “broker” functie werkt. Dus geen Datacollectors meer. FMA werkt met een “agent” functie, op de server of desktop wordt een agent geïnstalleerd waarmee het een onderdeel wordt van de Citrix omgeving. Het geeft daarmee voor XenApp net als in eerdere versies van XenDesktop ook de mogelijk gebruik te maken van de deployment oplossing van Machine creation services (MCS). Vanzelfsprekend is nog wel steeds remote desktop services nodig. Hieronder een overzicht van de FlexCast management architectuur.


FlexCast Management Architecture.png

Afbeelding 1: FlexCast management Architecture

Citrix Hybride Cloud Provisioning

Een van de zaken die er in de nieuwe release van beide producten in zit is het Hybride Cloud Provisioning. Dit geeft de mogelijkheid om bij het aanmaken van een machine pool dit niet op de bestaande lokale infrastructuur te doen maar direct naar de Cloud. Zo kan het schalen van een Citrix infra gecombineerd worden met Cloud resources. Het uiteindelijke resultaat moet zijn dat een omgeving schaalbaar en flexibeler wordt voor elke situatie.
Hybrid Cloud Provisioning.jpg
Hybride Cloud Provisioning

Remote PC Access

Al eerder aanwezig in XenDesktop maar nu ook terug te vinden in beide nieuwe releases is Remote PC Acces. Citrix remote pc acces geeft de mogelijkheid om een fysieke pc of elke andere pc of virtuele desktop os te voorzien van agent om vervolgens remote via de bestaande Citrix infrastructuur beschikbaar te maken. Hiermee kunnen bijvoorbeeld fysieke beheer werkplekken via Citrix beschikbaar gesteld worden. Het is ook ideaal voor de start met VDI zonder direct een complete VDI omgeving te moeten investeren. Er kan gewoon op de bestaande fysieke desktop doorgewerkt worden. Door een koppeling met System center Configuration Manager 2012 R2 te maken kan er zelfs met wake on lan gewerkt worden.
Remote PC Access Citrix.jpg
Afbeelding 2: Remote PC Acces

Upgrade path XenDesktop en XenApp 7.5

Upgrade path van bestaande Citrix omgeving naar de XenDesktop en XenApp versie 7.5 is zoals hieronder te zien is in de tabel in veel gevallen mogelijk door middel van een upgrade. Alleen bij de oudere versies van XenApp en XenDesktop is een nieuwe farm en dus migratie nodig. Overigens is het advies nooit een upgrade te doen tenzij de omstandigheden of grootte dit niet toelaten.
XenApp Upgrade Path.png
XenDesktop Upgrade Path.png

Storefront 2.5.

Met de nieuwe release van XenApp en XenDesktop is er ook een nieuwe versie van storefont gekomen versie 2.5. Ondanks de nieuwe release van Storefront en de mogelijkheden en daarmee het advies van Citrix om toch vooral naar storefront te gaan heeft Citrix de support van de oude webinterface versie 5.4 verlengt. Dit is gedaan om beheerders meer tijd te geven te migreren naar Storefront maar ook om de beheerders de kans te geven meerdere en vooral oude en nieuwe farms eenvoudig door elkaar te kunnen draaien om de migratie weer minder spannend te maken. Storefront 2.5 bevat wel de nodige verbeteringen die de migratie naar Storefront meer en meer de moeite waard maken. Een van de belangrijkste is toch wel het single sign on deel. Dit maakt het mogelijk om een gebruiker vanaf een domain joined systeem van buitenaf (via de NetScaler) met internet Explorer via het web applicaties zonder nieuwe authenticatie te laten starten. Deze verbetering is een echte klant wens en in veel gevallen een rede geweest om te wachten met de migratie naar storefront. In de nieuwe release van storefront zit eveneens een verbetering van de HTML5 receiver. Deze receiver speciaal ontwikkeld voor de Chromebook is ook handig in andere externe inlog mogelijkheden zoals een internet café. De verbeteringen in de HTML5 receiver zitten hem voornamelijk in de verbeterde ondersteuning van 2D en 3D applicaties maar ook audio is enorm verbeterd.
HTML 5 Receiver.png
Afbeelding 3: HTML5 Receiver
In de totale lijst van vernieuwingen en verbeteringen zijn geen spectaculaire zaken terug vinden. Dit was ook niet te verwachten. In de beide releases zijn vooral op kleine zaken enorme verbeteringen doorgevoerd. Al deze kleine zaken hebben echter wel een compleet beter resultaat op zowel beheer als de gebruikers ervaring. Zo zijn er verbeteringen in de touch ervaring op touch enabled devices en is er opnieuw veel aandacht uitgegaan aan de mogelijkheden over WAN en high latency verbindingen met zware 2D en 3D ondersteuning (server side rendering) want beide release meer dan de moeite waard maken.
Bent u geïnteresseerd in de nieuwe releases van XenApp en XenDesktop of heeft u vragen over de mogelijkheden van Citrix voor uw organisatie? Dan kunt u contact opnemen met Carlo Schaeffer via of bellen naar 010 – 750 45 90.

Cool new Windows 8 VDI and RDS capabilities!

Windows Server “8” Beta, has a lot of new Remote Desktop Services, VDI and administration capabilities to simplify deploying virtual machine-based and/or session-based desktops or applications. This includes new features related to pooled deployment (single virtual desktop template across many users), personal desktops (one VHD per user), and user profile disks.

Adam Carter has created a brief video to overview the above new features of Remote Desktop Services (not a complete list of all new features) on the Edge Show. A must see video.

Edge Show 16 – Windows Server 8 VDI

Windows 8 Consumer Preview (Desktop and Server) now available for Download

And if you want some videos:

Windows 8 Desktop Consumer Preview ISO files (.iso) are provided as an alternative to using Windows 8 Consumer Preview Setup. If you are on a PC running Windows and want to install the consumer preview on another partition, another PC, or a virtual machine, i recommend you download Windows 8 Consumer Preview Setup and use the built-in tools for converting an ISO image into installation media, such as a DVD or USB bootable flash drive. You can find additional information, including a list of supported upgrades, in the FAQ.

English 64-bit (x64) Download (3.3 GB) Sha 1 hash — 1288519C5035BCAC83CBFA23A33038CCF5522749

English 32-bit (x86) Download (2.5 GB) Sha 1 hash — E91ED665B01A46F4344C36D9D88C8BF78E9A1B39

Product Key: DNJXJ-7XBW8-2378T-X22TX-BKG7J

The next release of Windows Server, Windows Server “8”, offers businesses and hosting providers a scalable, dynamic, and multitenant-aware, cloud-optimized infrastructure. It securely connects across premises and allows IT Professionals to respond to business needs faster and more efficiently. Register to access technical product resources such as forums, solution accelerators, white papers and webcasts at the Windows Server “8” Beta Resource Page.

Download here: Link

Windows Server “8” beta documentation site is updated, here are some links:

Remote Server Administration Tools for Windows 8 Consumer Preview includes Server Manager, Microsoft Management Console (MMC) snap-ins, consoles, Windows PowerShell cmdlets and providers, and command-line tools for managing roles and features that run on Windows Server “8” Beta. In limited cases, the tools can be used to manage roles and features that are running on Windows Server 2008 R2 or Windows Server 2008. Some of the tools work for managing roles and features on Windows Server 2003.

Download here: Link

The Windows 8 Consumer Preview Product Guide for Business provides a detailed look at the many new and improved features in Windows 8. The guide is designed as an accurate source of information that can help businesses understand how Windows 8 enables users to be ready and productive practically anywhere, allows for a personalized user experience, and provides IT with more secure, easy-to-manage intelligent infrastructure.

Download here: Link

Remove Favorites, Libraries and Network from Windows 7 / 2008R2 Common File Dialog (Windows Explorer)

Within Windows Explorer you got the common file dialog (Shown @ the screenshot below). Within this dialog you got a favorite link, a Libraries link and a network link. These links are in some cases a security problem. You don’t want users to use the libraries folder witch contains all users folders when they work on systems that share users for example XenApp servers. Also you don’t want users to browse the network or see auto discovered server names…Here is described how you get rid of it!

You can set these registry settings within the 2008 computer policy’s with the registry but there is a problem with the rights. Standard the system and the administrators don’t have rights to set the settings. You have to change the acl to set the registry keys!

1. To remove the Favorites, the key is:


Changing a0900100 to a9400100 will hide Favorites from Navigation Pane.

2. For Libraries, the key is:


Changing b080010d to b090010d will hide Libraries from Navigation Pane.

3. For Network, the key is

“Attributes”=dword: b0940064

This first part is, in the 32-bit world, the solution for the Windows Explorer ánd the Common File Dialog. But in the 64-bit world you need another registry key edited. This is basically the same key, but in the Wow6432Node ‘folder’ within the registry.
The trick!:

1. To remove the Favorites X64 , the key is:


Changing a0900100 to a9400100 will hide Favorites from Navigation Pane.

2. For Libraries X64, the key is:


Changing b080010d to b090010d will hide Libraries from Navigation Pane.

3. For Network X64, the key is

“Attributes”=dword: b080010d

Changing b080010d to b090010d will hide Libraries from Navigation Pane.

Exchange 2010 SP1 gives Multi-Tenant support

Exchange 2010 SP1 has built-in multi-tenant support, which helps service providers to host multiple organizations in a single Active Directory environment. There are few features which are available only in hosting mode and few others which are not available, compared to a normal deployment of Exchange 2010 SP1. 2010 SP1 will form part of the suite of multi-tenant capable products that will replace the Hosted Messaging and Collaboration solution.

Few points to note about installing 2010 SP1 in hosting mode:

  • The installation can only be done in command line.
  • You need to use /InstallWindowsComponents while running the setup to install all windows components required for Exchange. This will not install the pre-requirements only the windows components! Always install the pre-requirements first.
  • You need to use /Hosting switch while running the setup to install Exchange in hosting mode.
  • 2010 SP1 is required.
  • Exchange Management Console will not be installed.

Exchange 2010 SP1 doesn’t support the following features in Hosting mode (from Technet):

  • Exchange Management Console
  • Public Folders
  • Unified Messaging Server role
  • GalSync
  • Federation
  • Business-to-Business features such as cross-premises message tracking and calendar sharing
  • IRM
  • Outlook 2003 support (EnableLegacyOutlook)
  • Edge Transport Server role
  • Same forest upgrade from Exchange 2007
  • Resource forest
  • Parent-child domains
  • Discontiguous namespace
  • Disjoint namespace

Here is based on the blogs zerohoursleep and howexchangeworks how its done! This step-by-step tutorial that will guide you to installing your first Exchange 2010 SP1 multi-tenant organization to a fully operational mode.

Lab setup

For this lab I am using 2 servers running Microsoft Windows 2008 R2 one of them acting as a domain controller for the lab domain and the other will be running all roles of Microsoft Exchange 2010 SP1 CAS,HUB and Mailbox.

Of course in a live environment exchange roles will be most probably split among multiple servers but the concept is pretty much the same.

I will assume that the Domain Controller is already installed and that the exchange server to be has already Windows 2008 R2 installed with all the required patches to deploy Exchange 2010 SP1.

Installing Exchange 2010 SP1 in hosting (or multi-tenant) mode

Installing Exchange prerequisites on Windows 2008R2

I am used to this script to automate installation of the prerequisites since I find it very clean.
We will start by running the powershell administrator “right click -> run as administrator” and allow the script execution using

Set-ExecutionPolicy unrestricted

Running the script will then offer you a menu, in my case I need to select option 6 since all roles will be installed on the same server and restart the machine after.


Installing Exchange

As you may already know Exchange 2010 multi-tenant can only be installed using the command line by adding the /hosting parameter, we will initiate the installation by running /m:install /r:m,ca,ht /installwindowscomponents /hosting /on:ExchLab


Let me first explain the above command

  • /m stands for /mode and we are running the installation mode
  • /r stands for /roles and we want to install the m (mailbox) ca (client access) ht (hub transport) roles. Of course you will need to change this if you don’t want to install all roles
  • /hosting is required to tell the setup to run the hosting installation
  • /on stands for /OrganizationName and you will define here the name of your Exchange organization. I called mine ExchLab

We will now wait for the installation to finish


A few differences with Exchange not hosted

The first thing I have noticed after the installation is differences in Active Directory Users and Computers like the presence of a brand new Organizational Unit “Microsoft Exchange Hosted Organizations”

And the addition of new Exchange Security groups (plus the absence of the UM one)

Now of course the absence of the Exchange Management Console should have been first however this I was expecting since it is all over the place so I was expecting this.

Continue reading