2008R2

Enable RemoteApp on Server 2008/Windows 7

2012-07-09
/ / /
We have two Citrix farms, a XenApp 5 farm and a XenApp 6 farm.  XenApp 6 only supports 64bit OS’s.

We have some applications that will not operate on a 64bit OS (Microsoft FRx).  Since we want to decommission our old Citrix XenApp 5 farm because we’re moving to XenApp 6/6.5 we need a solution.  The solution I have come up with is to use Microsoft RemoteApp functionality to publish this application through XenApp 6.  I’ve come across this blog post that details how to do it, but I’m going to summarize the technical changes here:

Step 1
Run regedit (registry editor) and locate the key TsAppAllowList
     a) New KeyApplications.
     b) Under Applications, create New Key1234567 (the key name is not important, we just need any key for next two steps)
     c) In the new key, Create New -> String ValueName. Set value to Notepad
     d) Also in the new key, Create New -> String ValuePath. Set to c:windowssystem32Notepad.exe

Navigate back to the TsAppAllowList branch
     a) Edit fDisableAllowList value, and set to 1


Step 2 – Creating the RDP file to access the RemoteApp
Now the guest operating system has a RemoteApp created we need to use a Remote Desktop Connection to access that application.
1. Run remote desktop connection, setup your desired settings as you would in a normal connection
2. Save the settings to an RDP file.
 
3) Use Notepad to open the RDP file to edit the configuration file,
   a) Modify the setting; remoteapplicationmode:i:0  to  remoteapplicationmode:i:1
   b) Add the setting; remoteapplicationprogram:s:Notepad
   c) Add the setting; disableremoteappcapscheck:i:1
   d) Add the setting; alternate shell:s:rdpinit.exe
   e) Save the RDP file

Final thought
Similar to VirtualBox seamless mode, you will not be able to move the floating guest application window between monitors, unless you save the RDP to use all monitors available.  Either set this option prior to saving the RDP file, or edit the RDP setting multimon:i:1.

Read More

AppV and Application Compatibility

2012-03-13
/ / /
I was having an issue with a old application that we want to run on our Citrix XenApp 6 farm; Microsoft Enterprise Reporting 7.5 SP4 (7.5.303). Namely, it wouldn’t run. It’s not compatible with Server 2008 R2 unless you’re running SP5. Well, we’re going to get rid of it in a few months but we want to get rid of our 4.5 farm. So, we need to migrate the application to XenApp 6 and Server 2008R2 from Presentation Server 4.5 and Server 2003 SP1.

First thing I did was setup a Server 2003 SP1 box and installed the AppV sequencer on it and sequenced the application. I then set it to run on 2008R2 64bit and moved the package over to it. It would crash. Analysing the crash logs would present to me the error… ERAPP32 was crashing its heap. In order to get it to work I had to set it to run in compatibility mode for XPSP3. Once I set this it worked flawlessly. So what I needed to do was push this fix to the rest of our Citrix servers before deploying the AppV application. If you’ve ever read ACT (application compatibilty toolkit) and merging it with AppV it’s kind of a difficult job.

But there is a easier way.

Stored in the registry is the AppCompatFlags key that contains the applications and the shims you can apply to an application. If you put the path to your AppV application it will actually enable it to run in the compatibility mode that you specify. This was my registry entry:

And now the application works almost wonderfully (ER is a painful application)

🙂

Read More

Windows Backup Error 0x81000019

2010-12-12
/ / /

Recently, I’ve been getting an error from Windows Backup:

Error Code: 0x81000019
Event Viewer lists the following additional information:
Shadow copy creation failed because of error reported by ASR Writer. More info: The requested system device cannot be found. (0x80073BC3).
 
Volume Shadow Copy Service warning: ASR writer Error 0x80073bc3. hr = 0x00000000, The operation completed successfully.
.
 
Operation:
PrepareForBackup event
 
Context:
Execution Context: ASR Writer
Execution Context: Writer
Writer Class Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Name: ASR Writer
Writer Instance ID: {5c8b67a8-a665-45e5-9f5c-45382f136693}
 
Error-specific details:
ASR Writer: The requested system device cannot be found. (0x80073BC3)
 
Volume Shadow Copy Service error: Unexpected error calling routine Check OnIdentifyError. hr = 0x80073bc3, The requested system device cannot be found.
.
 
Operation:
PrepareForBackup event
 
Context:
Execution Context: ASR Writer
Execution Context: Writer
Writer Class Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Name: ASR Writer
Writer Instance ID: {5c8b67a8-a665-45e5-9f5c-45382f136693}
 
Error-specific details:
ASR Writer: The requested system device cannot be found. (0x80073BC3)
 
Fault bucket 668258104, type 5
Event Name: WindowsBackupFailure
Response: Not available
Cab Id: 0
 
Problem signature:
P1: Backup
P2: 6.1.7600
P3: 0x81000019
P4: 7
P5:
P6:
P7:
P8:
P9:
P10:
 
Attached files:
C:\Windows\Logs\WindowsBackup\WindowsBackup.1.etl
 
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_Backup_7a9178ddfcd376c581a8653b09ae5e2464735bf_100ef6dc
 
Analysis symbol:
Rechecking for solution: 0
Report Id: 8b57e781-0633-11e0-a042-90e6ba2d22c8
Report Status: 0
 
Backup did not complete successfully because a shadow copy could not be created. Free up disk space on the drive that you are backing up by deleting unnecessary files and then try again.
And what does it all mean? Well, I just recently installed a new hard disk and installed an alternative OS onto it. This new hard disk is appearing as “Disk 0” in Disk Management and it *is* the boot device. When I boot off it and then select my Windows partition I get these error messages. It appears VSS attempts to access/lock the drive that booted the OS and it fails. If I attempt to take “Disk 0” offline, I get the following error message:
—————————
Virtual Disk Manager
—————————
Disk attributes may not be changed on the current system disk or BIOS disk 0.
—————————
OK
—————————
Using Procmon I can see that VSSVC.exe attempts to access a filesystem that it cannot… Well, the only disk that it can’t access is the lone “Alternative OS” disk. I suspect removing that disk or forcing my BIOS to boot directly to the Windows partition will resolve my issues. If you’re in a similar situation as me, I would suggest checking your boot order, removing any extraneous disks or ensuring your boot drive is appearing as “Disk 0” in disk management.
I’ve just tested and confirmed that forcing my BIOS to boot directly to my OS drive without going through an alternative drive has enabled the backup program to operate without any errors.
This blogpost is for anyone else that my experience a similar issue.
Read More