Windows cannot connect to the printer – error 0x00000006


Environment:

  • Windows Server 2008 R2 SP1
  • Citrix XenApp 6.5 RU5

Issue:

Attempting to add a network printer the following error is displayed

  • “Connect to Printer. Windows cannot connect to the printer. No printers were found”
  • Operation failed with error 0x00000006

Resolution:

Microsoft’s resolution for this issue is to install KB2778831, however there are instance of this hotfix being applied and the issue still occurring.

Manual Fix:

  1. Open Registry Editor
  2. Browse to HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers
  3. Back up then delete the Client Side Rendering Print Providers key
  4. Restart the Printer Spooler service
  5. Printers should now add successfully

Local Printer not printing in Citrix XenApp session


Environment:

Windows Server 2008 R2 SP1

Citrix XenApp 6.5

Local HP Printer

Configured Policies:

– Auto-create client printers: (Auto-create the client’s default printer only)

– Automatic installation of in-box printer drivers (Disabled)

– Universal driver preference (EMF;XPS;PCL5c;PCL4;PS)

Issue:

User has a local printer and logs into a Citrix desktop\application. The policy is configured to map through user’s local default printer. The printer maps through and appears in the users session. User prints to the local printer, print job spools, disappears and nothing prints out.

 

Resolution:

Reconfigured the ‘Universal driver preference’ driver order from

EMF;XPS;PCL5c;PCL4;PS

to

PS;XPS;EMF;PCL5c;PCL4

Citrix Storefront – HTTP Error 503. The service is unavailable.


UPDATED

Issue

Service Unavailable

HTTP Error 503. The service is unavailable.

Event Viewer error

Source: IIS-W3SVC-WP

Event ID: 2293

Description: The Module name ManagedEngine64 path C:\Windows\Microsoft.NET\Framework64\v2.0.50727\webengine.dll returned an error from registration.  The data is the error.

Application Pool ‘DefaultAppPool’ won’t start.

Resolution

Browse to: %Windir%\system32\inetsrv\config

Backup the ApplicationHost.config file

Open ApplicationHost.config

Look for <add name=”ManagedEngine64″ (around line 267) and delete the whole line

<add name=”ManagedEngine64″ image=”%windir%\Microsoft.NET\Framework64\v2.0.50727\webengine.dll” preCondition=”integratedMode,runtimeVersionv2.0,bitness64″ />

Save the file and run IISRESET

 

The cause was related to the fix of making the Storefront console load faster, by putting <generatePublisherEvidence enabled=”false”/> into C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet.config or c:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet.config

 

This fix is still valid but needs to be done AFTER installing and configuring Storefront the first time.

Automatically deploy SSL Certificates to Users profile


1. Deployment ScriptsUpdate the variables between <……>

Script 1 – ImportPFX.vbs

Set objShell = CreateObject(“Wscript.shell”)objShell.run(“powershell -executionpolicy bypass -windowstyle hidden -file \\<domain>\netlogon\Certificates\ImportPFX.ps1”)

 

Script 2 – ImportPFX.ps1

function Import-PfxCertificate {

param([String]$certPath,[String]$certRootStore = “CurrentUser”,[String]$certStore = “My”,$pfxPass = $null)

$pfx = new-object System.Security.Cryptography.X509Certificates.X509Certificate2

if ($pfxPass -eq $null) {$pfxPass = read-host “Enter the pfx password” -assecurestring}

$pfx.import($certPath,$pfxPass,”Exportable,PersistKeySet”)

$store = new-object System.Security.Cryptography.X509Certificates.X509Store($certStore,$certRootStore)

$store.open(“MaxAllowed”)

$store.add($pfx)

$store.close()

}

#*=============================================================================

#* SCRIPT BODY

#*=============================================================================

# Call the “Import-PfxCertificate” function.

Import-PfxCertificate “<path to certificate>\<Certificate.pfx>” “CurrentUser” “My” “<password>

Import-PfxCertificate Command Syntax

Import-PfxCertificate

<path to certificate>\<Certificate.pfx>” = Location of the Certificate File

“CurrentUser”                                                        = Personal User Store

“My”                                                                           = Personal Cert Store

<Password>”                                                       = Password of the PFX Certificate

2. Deploy Script via GPO

I created an additional GPO and modified the Logon Script path to run the vbs file above.

User Configuration > Policies > Windows Settings > Scripts > Logon

– Script Name: \\<domain>\NETLOGON\Certificates\ImportPFX.vbs

2a. Apply Security to GPO

In our case we wanted to deploy the certificates to users in a certain AD Group.

Follow this procedure exactly otherwise the GPO won’t apply

  1. Under Security Filtering leave Authenticated Users, do not remove!!
  2. Click Delegation tab
  3. Click Advanced button
  4. Select Authenticated Users, untick ‘Apply Group Policy’ under Allow only
  5. Add in AD Group, tick ‘Apply Group Policy’ under Allow
  6. If you go back to Security Filtering you’ll notice Authenticated Users has now gone and your AD Group is listed, don’t worry about this..

“The display settings can’t be changed from a remote session”


Issue

When selecting “Make text and other items larger or smaller” the option is greyed out and displays “The display settings can’t be changed from a remote session”.

Yet another option Microsoft has removed the ability to do. This option was available in Windows 2003 Terminal Services.

Resolution

Microsoft have released a hotfix that re-enables this option again for users

http://support.microsoft.com/kb/2726399

Error: Shadow failed. Error code 120


Issue

When trying to shadow users with multi-monitors you get an Error Code 120.

Resolution

There is no Citrix resolution for this, it’s a Microsoft RDS issue which effects XenApp shadowing (http://support.microsoft.com/kb/2484290)

Microsoft workaround for this is to install Remote Assistance and use this tool for Shadowing (http://support.citrix.com/article/CTX125693)

Error – The account is not authorized to log in from this station


Environment

MDT Deployment Toolkit 2012 (Update 1)

Building Windows Server 2008 R2 SP1

 

Issue:

Once the server has completed the build, you’re unable to browse to certain CIFS shares like profile or home directories, the error is The account is not authorized to log in from this station.

 

Resolution

Within MDT 2012 using the default Standard Server Template it runs ‘Apply Local GPO Package’ which applies local GPO’s supplied with MDT. 

Disable this job and it will resolve that error message.