Hi it’s me Al,
This is a quick post how to use DISM Online to change the product key of a Windows Server 2012 R2. Sometimes you’re not able to change the key using the GUI. This is how to do this using DISM:
1. Run powershell or a cmd as Administrator
Use DISM /online /Get-TargetEditions to list available editions for upgrade. To upgrade from evaluation to standard use DISM /online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula
2. Use the command DISM /online /Set-Edition:ServerDatacenter /ProductKey:XXXX-XXXXX-XXXXX-XXXXX-XXXXX/AcceptEula
3. Reboot the Server
Hi, When you check for new builds of Windows 10 Technical Preview, you’re not offered with the new Build 10041. You already tried to change the settings here: Settings > Update & Recovery > Advanced options, and setting Choose how preview builds are installed to Fast. Solutions: Option 1: Install the Windows Update that will reset your Flight Registry Settings You can download the update directly from the Microsoft Update Catalog:
Option 2: Edit your registry If you’re not able to install the update, you can instead edit the registry yourself. A word of warning: these instructions ONLY apply to devices on Build 9926 that have set Choose how preview builds are installed to Fast: Continue reading “Windows 10 Technical Preview not offering the new Build 10041”
During a VDI deployment by one of our customer we ran into an issue with the RDS Connection Broker in HA mode. The user were unable to login to the pool.
The error in the RD Management Server Event Log showed up with Config sync failed. Following error occurred: 0x88250001
One of the reason causes this issue was the Licenensing Server which did not have a User or Device selection. So we changed that to “User” for our case.
But after this, users where still unable to login.
To get rid of this error, change the active Connection Broker Server using the Remote Desktop Management Admin Console:
Deployment Overview – Tasks – Set Active Remote Desktop Connection Broker server
This solved the logon problems to the VDI Pool.
Hope this helps someone.
Hi geeks out there,
Today I was running into an issue publishing an old legacy application as a RemoteApp. The application is located on a network share with several parameters. A network drive also has to be mounted.
On the first RD SH I created a shortcut with all the parameters pointing to the application and tried to publish this using powershell. But the application did not start. After that I tried several other powershell command with no luck.
Finally I created a .cmd file on the local RD SH with the the command:
On the Connection Broker I used following PowerShell Command to implement the application as RemoteApp:
New-RDRemoteApp -Alias “AliasName” -CollectionName “CollectionName” -DisplayName “DisplayName of the App” -FilePath “C:Sourcestoyourcmd.cmd” -IconPath “C:SourcesyourICO.ICO”
Make sure you create all the source files on all the session host in the collection.
Hope this helps!
Hi – It’s me, Al
Blog post updated: July 19th 2017
Remote Desktop Services (RDS) on Windows Server 2012 R2 is now on market since a while. Let’s have a look at the 2012 R2 Certificate configuration (for a Lab).
First we have to create a template on the internal Certificate Authority (CA). We use a Workstation Authentication Template for that. Open your CA Manager – Cartificate Templates – Manage
Duplicate the “Workstation Authentication” Template.
Continue reading “How to deploy Remote Desktop Services 2012 R2 Certificates using internal CA #RDS”