Microsoft has released a new version of Microsoft Server 2016 Technical Preview 2, so I’ve installed this version immediately within my Hyper-V environment. After starting the setup, you’ll see there’re two versions:
Windows Server Technical Preview 2
Windows Server Technical Preview 2 (with local admin tools)
The difference between theese two versions is the User Experience. In previous version of Windows, it was called Windows Server Core Edition. So the version without the local admin tools, the user has no option to enable/install the graphical user interface (GUI).
After the installation, you’ll see that there’s a difference between the User Experience. One version, the Server Manager is available and the other version has only a command prompt available. You’ve to manage this server from another server with the Remote Server Administrative Tools (RSAT). The version with the admin tools included, there’s a possibility to enable the Graphical User Interface (GUI).
After a reboot, the server is turned on with a Graphical User Interface (GUI) and it looks pretty cool!! And YESSSS, the start menu is back again What a great time for some users!! With this new version of Windows Server, there’s is a complete new “world of bits and bytes”….
Microsoft has released a great free Ebook of how to Deploy Hyper-V with Software-Defined Storage & Networking (SDN). In this Ebook you’ll learn all the basics of Software Defined Datacenter and how to use it in real life!
During a deployment of Microsoft Windows 8/8.1, you’ll receive a question to select a prefered network connection. This is also happening during a task sequence within Microsoft SCCM 2012 R2. It’s easy to disable this
question during the task sequence, using an unattend XML file.
1.) First open the “Windows System Image Manager”, also known as WSIM
2.) Select the image you want to deploy. In my example “Install.WIM” from the Windows 8.1 source files
3.) Create a new catalog for this image
4.) After the catalog has succesfully created, create a “New Answer File”
5.) Navigate to the following selection
6.) Select the “+” on the left side and naviagte to “OOBE”
7.) Right-click on “OOBE” and select “Add Settings to Pass7oobeSystem
8.) Select in the right pane OOBE
9.) Select in the properties pane “HideWirelessSetupInOOBE” and set the value to “True”
10.) Save the XML file on your “source” directory on your primary site server
11.) Create a new package with the source directory to the directory you’ve created in the stap before
12.) Do NOT create any program in the package, so select “Do not create a program”
13.) Distribute the new package to your distribution point(s)
14.) Open your task sequence and navigate to stap “Apply Operating System”
15.) Select the option “Use an unattended or Sysprep answer file for a custom installation
16.) Select the package you’ve created before and type the name of your XML file within that package source location
17.) Boot a client from the network (PXE) and select the task sequence.
If you follow the steps within the task sequence, you’ll see that you didn’t receive a network connection screen anymore.
When you install a default Windows 8.1 machine, there’re a few modern apps available. In some environments, you want
to remove these modern apps for your users.
With the following steps, you can delete specific apps or all the modern apps.
1.) To get a overview off all the package, use the following command:
Get-AppxPackage | ft Name, PackageFullName -AutoSize
2.) Let’s remove the Finance modern app
Remove-AppxPackage -Package Microsoft.BingFinance_22.214.171.124_x64__8wekyb3d8bbwe -Confirm:$false
3.) Return to the start menu and now you’ll see the Finance app is gone
4.) To remove all the modern apps, use the following command:
Get-AppxPackage | Remove-AppxPackage -Confirm:$false
Today I had to move the library of the Distribution Point to another partition, because it was placed on the wrong partition during the install.
During the installation of ConfigMgr 2012 R2 (or ealier), you can place a file “no_sms_on_drive.sms” on the partitions that should be ignored for placing the library on.
In this environment there’s a C:, D: and E: drive. The C: partition is only used for the operating system. The D: drive is used for the installation of
ConfigMgr 2012 R2, SQL 2012 and the remote installation folder of WDS. The E: drive is used for the sources, images, ISO’s and the library of the Distribution Point.
So I want to move the library from the D: to the E: partition. First you’ve to download the “System Center 2012 R2 Configuration Manager Toolkit”. http://www.microsoft.com/en-us/download/details.aspx?id=36213
1.) Open REGEDIT and navigate to HKLM\SOFTWARE\Microsoft\SMS\DP and look for the registry key
“ContentLibraryPath” and “ContentLibUsableDrives”
2.) When you open Windows Explorer and browse to the D: drive, you’ll see the library folders SCCMContentLib SMSPKG SMSPKGD$ SMSPKGSIG SMSSIG$
These folders we want to move to the E: drive
3.) Open the command prompt and navigate to C:\Program Files (x86)\ConfigMgr 2012 Toolkit R2\ServerTools\”
4.) Use the following command to move the Library content from D: to E: ContentLibraryTransfer.exe -SourceDrive D -TargetDrive E > C:\TransferContentLibrary_log.txt
5.) Start CMTrace.exe and open the logfile “C:\TransferContentLibrary_log.txt” to watch the progress of the library move
6.) After a few hours, depending on the size of your library content, the move action is done
7.) pen REGEDIT and navigate to HKLM\SOFTWARE\Microsoft\SMS\DP and look for the registry key
“ContentLibraryPath” and “ContentLibUsableDrives”
Now you’ll see only the E: drive for the Library placement
8.) I’ve have created the file “no_sms_on_drive.sms” on the C: and D: drive
When you have a Microsoft ConfigMgr 2012 or 2012 R2 environment, you definitely have a lot of packages and applications. This could be: tools, scripts, client packages, boot images, ISO’s, WIM files, different software applications, etc. When you have no idea where all these source files are located, you can execute a query within your SQL environment.
You can generate an overview of all your packages, with the package ID, description, name, source location, version, etc. Very helpfull and it saves you alot of time!!
1.) Open the Microsoft SQL Server Managent Studio
2.) Login with a user that has enough rights to execute queries
3.) Select the ConfigMgr database (in my example CM_PS1)
4.) Select “New Query”
5.) Type “SELECT * from v_Package”
6.) Select “Execute” or press F5 on your keyboard
7.) Now you’ll see a list off all the packages within your ConfigMgr 2012 environment
8.) Navigate to the table “PkgSourcePath”
9.) Here are your source files locates of all the different packages
When you setup coexistence with Microsoft Exchange 2010 and 2013, you can manager you mailbox databases in different ways. Though the Exchange Management Console (EMC), Exchange Control Panel (ECP) or with Exchange Management Shell (EMS). Today I had to configure a new Microsoft Exchange 2013 environment in a existing Exchange 2010 environment, so this is a coexistence infrastructure.
When I had installed the new Exchange 2013 servers, and I had started the Exchange Management Shell (EMS) from the new Exchange 2013 server, I saw only the new Exchange 2013 database. But wait a minute, I had also a copple of mailbox databases configured on my existing Exchange 2010 environment. In the Exchange Control Panel (ECP), all the databases are visseble, but why not in the Exchange Management Shell?
The solution is pretty easy. Within Exchange 2013 there’s a new parameter that you can use with the Get-MailboxDatabase command. So the new parameter is -IncludePreExchange2013. The whole command should be: Get-Mailboxdatabase -IncludePreExchange2013.