Windows 2008

My Windows 2008 experience on daily basis and troubleshooting steps.

Process CSRSS.EXE remains when a Sessions is logged off

Summary: I’m working on an  issue with Citrix XenApp 6.5 on Windows 2008 R2 SP1 where sessions remain after a user logs out. We have a number of different environments all running the same version of Citrix and OS. The troubleshooting begins!

Please see my earlier post, this issue remains, “Down Session and Multiple Instances”

Environment:

OS: Windows 2008 R2 X64 SP1 Enterprise

Citrix: XenApp 6.5

Hardware: Blade

IMPACT: Users logging out of Citrix may end up with multiple sessions and multiple processes which are not visible to the user, meaning less resources on the server until the memory and CPU max out and a reboot is required.  This can also affect applications that are license dependent, using up licenses for dead sessions.

 

Troubleshooting: The first question you have to ask yourself:: Is this a Microsoft or Citrix Issue? The CSRSS.exe is a Microsoft component “Client/Server Runtime subsystem” is mainly responsible for Win 32 Console handling and GUI shutdown, terminating this task will cause a BSOD or the server to reboot. So I’m thinking this is more of an Microsoft issue.

Microsoft have already identified this as an issue in a hotfix before SP1 and it was meant to be included in SP1.

Google hasn’t produced any great results so I’ve open an case with Microsoft and we are now trying HOTFIX: KB2661332

I’ve also installed XenApp 6.5 Roll-up Pack 1

Watch this space to see if the issue has been resolved.

Windows must be reinstalled

I’m returning to a project I haven’t touch for a couple of months, purely down to the fact I have another 6 projects on the go. Anyway I’m testing RSA over Citrix and need a test Citrix server and there’s no point using a license for a non production server which will be scraped after testing is complete. So I have an evaluation version of Windows 2008 R2 and this morning I received the error “Windows must be reinstalled” An unauthorized a change was made to Windows. Windows must be reinstalled to activate. Insert the Windows installation DVD or CD into your computer to begin the reinstallation process.

 

Resolution:

  1. Open a “Run As Administrator” command window
  2. Type: cd %windir%\system32
  3. Type:cscript slmgr.vbs -rilc
  4. Reboot

Notes: I’ve seen other blogs with simlair issues on Windows Vista and licensed servers, I recommend you try this approch first as it can’t really do any harm. You will of course need to know your license keyif you have to reactivated. This approch worked for me, but there are no gauentees this will work in all enviroments.

Also See: How to extend the Windows Server 2008 evaluation period http://support.microsoft.com/kb/948472

The PIPE State is Invaild – Windows 2008

Today’s challenge is to investigate the cause of the User Profile Service failing.  My users recieve the message “Windows could not connect to the User Profile Service” in Citrix or “Failed to connect to a Windows Service” When using RDP.

When trying to restart the “User Profile Service” I recieve the message “The PIPE state is invaild”.

Most websites have sugguested rolling back in the case of Vista, I have not such an Options.

Trouble shooting steps:

  1. Check all event logs for the cause and Google for more background information.
  2. Restart the Server (Does this resolve the issue?) I’ll soon find out.

Looks like a reboot worked!

Windows 7 – NT backup

I’m in the very slow process of migrating over to Windows 7 from Windows XP. Although I don’t think I will ever completely stop using XP, because things just work!
Part of the process of migrating to 7 is to install the Windows Support Tools for Active Directory and Exchange 2003 system manager. These are challenges alone and I mite just have to deploy these tools over Citrix. Let see!
So I’ve backed up my old XP PC using NTBACKUP which millions of people would be doing over a number of years and I want to restore documents to my Windows 7 PC.
Where the hell is ntbackup? …………
Oh right its not included in Windows 7 so are we meant to keep using Windows XP for files restores?? Only if you have your backup on tapes, but not if you have your backup images on USB storage.
If your in the same boat as me you will find the following link useful, as Microsoft have offered ntbackup available as a download. http://support.microsoft.com/?kbid=974674

Please note this tool is only available for restores and not new backups.

This also applied to Windows 2008 R2

Windows 2008 DFS & VSS EventID:8193

I’ve been running into issues with DFSR and VSS which causes Shadow Copy Components backups to fail because one of the VSS writers had disappeared:

The Environment:
2 x Windows 2008 Enterprise x64 Servers
Hardware: Blades
Memory: 16GB
Disk Space: C: 40Gb, D: 100GB
Services: DFSR, Citrix XenApp 5.0, Netbackup, Terminal Server.

The Issue: Netbackup had been failing with ERROR 71 (Path not found) when we tried to backup Shadow Copy Component and we also noticed EventID: 8192 errors in the applications log from VSS. It appeared that the Shadow Copy Optimization Writer had disappeared from the list of VSS writers and this is netbackup’s API dependency.  In this case I opened a case with a Microsoft to troubleshoot further.

EVENTID: 8193

Netbackup Error: 71

Resolution: We were replicating with DFSR the local profiles for the Citrix Xenapp environment so that documents saved would appear in both location on Server A and Server B. The trouble with this method is that DFSR leaves open handles and as a result temporary profiles are created. In some cases the profile ID is locked and another one created, which in return renames the original profile id with a .bak extension in the system registry. When these backup profile IDs are created the Shadow Copy Optimization writer disappears from the writer list. I’m still asking the question to Microsoft how the profilelist and VSS “Shadow Copy Optimization” are dependant on each other.

It is NOT recommend to use DFSR to replication local user profiles i.e. C:\users and I have since removed this replication group. You will need to delete the .bak profile IDs from the following path in the registry:

\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

an example would be:  S-1-5-21-106000298-1275210071-1417001363-12345.bak

As with all system changes I would highly recommend exporting the keys or backing up the registry.

I’ve now decided to user Terminal Server user profiles with a path set to server A and this path is replicated to Server B using DFSR, with no further issues. For DR reasons the TS path  is actually a CNAME which I can change depending on server status and this was tested to work fine during fail-over.

Go to Top