Page 12

RD Connection Broker Config sync failed. Following error occurred: 0x88250001

Hi all,

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.

Solution:
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.

Cheers,
Al

Publish a legacy application on RDS 2012 R2 as RemoteApp

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:

start \serverc$sourcesyourInk.lnk

On the Connection Broker I used following PowerShell Command to implement the application as RemoteApp:

Import-Module Remotedesktopservices

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!

Cheers,

How to deploy Remote Desktop Services 2012 R2 Certificates using internal CA #RDS

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”

SCCM 2012 SP1 CU4 Client Update fails on Windows Server 2003

Hi – It’s me, Alain
A quick post: Today I was running into a problem upgrading Windows Server 2003 with the CU4 SCCM SP1 Client.

The Server startetd to install the Client but faild after a few minutes with following errors in the application eventlog:

.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) – Failed to compile: C:WINDOWSCCMSCClient.exe.config . Error code = 0x8007000b
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) – Failed to compile: C:WINDOWSCCMSCNotification.exe.config . Error code = 0x8007000b
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) – Failed to compile: C:WINDOWSCCMSCToastNotification.exe . Error code = 0x8007000b
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) – Failed to compile: C:WINDOWSCCMSCToastNotification.exe.config . Error code = 0x8007000b

Solution: Make sure you have .net 4 Framework installed. Uses this patch KB982671

http://support.microsoft.com/kb/982671/en-us

No reboot is required after installing the KB. Just make sure you’re refresh the maschine policy to install the client.

And please: Keep your systems patched :-).

Cheers,
Al

SCCM 2012 – Task sequence fails in SCCM if software updates require multiple restarts

Hi, I’m Alain Schneiter

This is my first post in this blog! I’m verry proud to be a part of this team.

Today we had the issue with a failing Tasksequence during the OSD of a Windows 2012 Server. The SMSts.log contained following error:

!sVolumeID.empty(), HRESULT=80004005
!sTSMDataPath.empty(), HRESULT=80070002
TS::Utility::GetTSMDataPath( sDataDir ), HRESULT=80070002
Failed to set log directory. Some execution history may be lost.
The system cannot find the file specified. (Error: 80070002; Source: Windows) Continue reading “SCCM 2012 – Task sequence fails in SCCM if software updates require multiple restarts”