How to: Install VMware Tools unattended using ConfigMgr 2012

When you’re deploying Windows 7 or Windows XP with ConfigMgr 2012 in VMware Workstation, you also need to install the VMware Tools. All the packages are installing silent/unattended, so we want to install the VMware Tools unattended to. Let’s do this…

1.) First of all create a new package. Navigate to Software Library, Packages
2.) Right-click and select Create Package
3.) Give the new package a name and select the Source Folder (this must be an UNC path)
4.) Choose the Standard program
5.) Give the new program a name and enter the Command line.
For 64 bits installation: setup64.exe /S /v” /qn REBOOT=R”
For 32 bits installation: setup.exe /S /v” /qn REBOOT=R”
6.) Optionally you can specify some requirements
7.) The next step is to deploy the package to the distribution point(s). This is a crucial step!!
8.) Richt-click on the package and select Distribute Content
9.) Select Add, Distribution Point or Distribution Point Group if you’re using more then one Distribution Point
10.) Select the your Distribution Point
11.) In the right corner you can see the content status. Wait until the content status is Success: 1
You can watch the logfile Distmgr.log to see the progres of the content distribution to your Distribution Point(s).
12.) The next step is to add the package to your Task Sequence or Deploy the package to your workstations.
13.) As you can see, the package is installed succesfully installed on my Windows 7 client whitout user interaction!!







ConfigMgr 2012 PXE-E3B: TFTP Error – File not found

A new feature within ConfigMgr 2012 is the PXE support on the Distribution Point Role. Yes, the PXE Service Point role is no more present within ConfigMgr 2012. The Windows Server Role Windows Deployment Services, also called WDS is still needed! Just install this role, do NOT configure the WDS server!

After enabling the PXE support on de Distribution Point server, the client should get the required PXE boot files. I received an error after the PXE boot “PXE-E3B: TFTP Error – File Not found”.

When I browse to the boot directory on my ConfigMgr 2012 server, all the folders were empty. The folders D:\SMSboot\x64 and x86 should be filled with the right PXE boot files. I forgot one critical step :S ….a new option in the properties of the boot images in ConfigMgr 2012 is “Deploy this boot image from the PXE service point”, located on the Data Source tab of the properties of the boot files.

After applying this changes on both boot files, the required PXE boot files were available in the right folders. My client are now able to PXE boot.




ConfigMgr 2012 SMS “The report service is not running on Reporting Service Point server” MessageID 7403

Today I had to install the reporing functionality within Microsoft System Center Configuration Manager 2012 (ConfigMgr 2012). First of all I’ve installed the SQL reporting services on the existing SQL server. Everything looks fine so far. After installing the Reporting Service Point from the ConfigMgr 2012 Management Console, there wasn’t any report!

The first you’ll need to watch, is the Component Status unther the Monitoring tab. There were several errors.
“The report server service is not running on Reporting Service Point server “SCCM-SQL01.SCCMLAB.local; start the service to enable reporting.”

This is really strange, because the SQL Reporting Webservice is running fine. I could browse to the default SQL reporting website and also the management website. The current version of my SQL environment was SQL Server 2008 R2 (10.50.1600)

After applying Service Pack 1 for SQL Server 2008 R2, everything works fine! The new version was 10.50.2500. I’ve downloaded Service pack 1 from the following URL:

Don’t forget to configure the right permissions to the Reporting Service User within de SQL Reporing Server.

1.) Open Internet Explorer
2.) Browse to the following URL: http://SQLSERVERNAME/Reports
3.) Select your ConfigMgr site
4.) On the drop-down list, select Security
5.) Select New Role Assigment
6.) Select the user name and configure the following roles:
– Browser
– ConfigMgr Report Administrators
– ConfigMgr Report Users
– Content Manager
– My Reports
– Publisher
– Report Builder
7.) Go back to your ConfigMgr 2012 server
8.) Select Monitoring, Reporting, Reports
9.) The reports are loaded now
10.) Select a report and hit Run





Installing Windows 8 Consumer Preview within VMware Workstation 8.0.1

Today i’ve installed the new Windows 8 Consumer Preview within VMware Workstation 8.0.1. I’ve executed the following steps.

1.) First of all you need to create a new virtual machine by choosing file, New Virtual Machine
2.) Choose Typical (recommended)
3.) Choose I will install the operating system later
4.) If you want to install the x86 version of Windows 8, you need to choose Microsoft Windows, Windows 7
5.) If you want to install the x64 version of Windows 8, you need to choose Microsoft Windows, Windows 7 x64
6.) Give the new VM a name and select the save location
7.) Modify the memory and optionally the processor and cores
8.) Attach the Windows 8 Consumer Preview ISO to the Virtual Machine
9.) Start the Virtual Machine.
10.) From now on it’s almost Next…Next…Next…Finish 😉

I’ll now what to do this evening…PLAYING WITH WINDOWS 8!!






How to: Move the transport queue on an Exchange 2007/2010 Hub Transport Server

When you’ve a large Exchange environment, it’s recommended to change the location of the Hub Transport queue. To do this, you can use the following script. The default location is the folder where you’ve installed Microsoft Exchange. For example C:\Program Files\…

1.) Navigate to the file EdgeTransport.exe.config, located in the Bin directory of the Exchange installation folder.
2.) Search for the rules QueueDatabasePath and QueueDatabasesLoggingPath. This is the orrigional location
3.) Open the Exchange Management Shell
4.) Browse to the scripts directory in the Exchange installation folder
5.) Select the script Move-TransportDatabase.PS1
6.) Run the following command
Move-TransportDatabase.PS1 -QueueDatabasePath NEWLOCATION -QueueDatabaseLoggingPath NEWLOCATION
In my example it’s moving to D:\Queue
7.) Now the Hub Transport database and logfiles will be moved to the new location. It’s containing the following files;

Trn.chk – The checkpoint file
Trn.log – The current transaction log file
Trntmp.log – The next provisioned transaction log file that is created in advance
Trnnnn.log – Other transaction log files that are created when Trn.log reaches its maximum size
Trnres00001.jrs – The Reserve log file
Trnres00002.jrs – The Second Reserve log file
Temp.edb – Temp DB used to verify database schema on start-up