Friday, August 30, 2013

Remote Desktop Services in 2012

In a customer environment they wanted to install RDS and DC on the same server. A nice cheap solution, which have worked perfectly fine in the past. Not so anymore. In Server 2012, RDS requires by default that
  1. A domain controller is present, aka server is member of a domain
  2. the RDS role cannot be installed on the DC
Which means, you need at least two servers for a working installation?
Well no, there is apparently a official workaround from microsoft. It was not easy to find so im posting it here for future reference or until I’ve had time to try it out.
Edit:  A colleague actually tried this out on several machines and it seemed to work as expected.
Solution: - Guidelines for installing the Remote Desktop Session Host role service on a computer running Windows Server 2012 without the Remote Desktop Connection Broker role service
References: - specs about rds 2012. - deprecated - changes - new ways of managing rds - – ms article regarding standalone rds

Thursday, August 29, 2013

Previous Version stopped working on network share

Environment: Server 2003 R2


No previous versions of files are found when looking from client computer on network share. Seems to be set up ok, but when looking at Task Scheduler the job shows error “Could not Start”


Event Viewer shows no related errors at the latest runtime.


  1. Disable shadow copy and delete all scheduled jobs.
  2. Delete or move files starting with “d42” from folder “C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\S-1-5-18”
  3. Enable shadow copy on disks and verify that task now can be started manually.


Might be the account originally used to create the job doesn’t exist anymore.

References: - 0x800700d data is invalid. -




Tuesday, August 20, 2013

Bulk creating and removing mailboxes

To create users in Exchange 2013, when they already exist in AD this script is useful.

foreach ($user in get-content users.txt)
Enable-mailbox –identity mydomain\$user –database mailboxdatabase1
write-host "$user is processed."

Users are stored in users.txt

To only remove mailbox, but not the AD-user from exchange. This is useful when needing to redo import if something didn’t land where it should.

foreach ($user in get-content DeleteUsers.txt)
disable-mailbox –identity mydomain\$user -confirm:$false
write-host "$user is processed."

Users are stored in DeleteUsers.txt

Each line contains one username.