Local Windows user profile corruption with SVS and Cisco Clean Access Agent
lidoiwo
March 20th, 2009
We are trying to deploy the Altiris Software Virtualization to start using svs packages. Users that have the SVS agent without any SV layers installed have no problems on bootup. It is when we deploy a SV layer to them Users begin having local profile corruption issues. We beleive it has something to do with the Cisco Clean access agent. The only information in the event logs is that the system can not load the users profile because it is in use by another. Our company deals with the government and the users are lockdown quite a bit. EyeBlink Professional, Pointsec Protector, Mcaffee and a host of login policies. Anybody out have an issue like this. Altiris support is stumpped.
About Endpoint Management and Virtualization Community Blog
The Endpoint Management & Virtualization Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Endpoint Management & Virtualization community. Any authenticated Connect member can contribute to this blog.
Filter by:
Blog Tags
7.1 Agents Altiris Client Management Suite Altiris Deployment Solution Altiris IT Asset Management Altiris Notification Server Altiris Recovery Solution Altiris Server Management Suite Asset Management Suite Backup Exec Backup Exec System Recovery Basics Best Practice Beta CIO Digest Case Study Compatibility Configuring Customer Preview Customer Reference Database Dell Dell Management Products Demonstration Documentation Downloads Drivers Emerging Threats Endpoint Management and Virtualization Endpoint Protection (AntiVirus) Enterprise Vault Error messages Evaluating Features General Symantec Ghost Solution Suite HP Management Products Helpdesk Solution How to ITMS Industry Event Inside Symantec Installing Licensing Linux Local DS GURU Email group Mac OS ManageFusion Mobile & Wireless NetBackup New Release News News Performance Platforms & Hardware Problem Management Recovering Reporting Restore SP2 SecurityExpressions Service Pack 2 ServiceDesk Storage Foundation Symantec Connect Symantec Event TMS TechTips Tip/How to Tips/How To Training Troubleshooting Upgrade User Group VDI VMware Virtualization Virtualization Vision Vulnerabilities & Exploits Windows Windows Wise Application Packaging Wise Installation Development Wise Virtual Composer Workflow Solution Workspace Corporate Workspace Profiles Workspace Remote Workspace Streaming Workspace Virtualization XPF baltimore deployment hugo known_issue pcAnywhere solution webcast
First check
When this occures, the best you can do is import the package on a clean machine.
Go to fslrdr directory and search up the number of the package. Go to the read/write layer and delete all sids that reside ther.
Then export the package.
You also could do it by renaming the exported package to zip, open it in winzip and go to 2. Then delete the sid that is in there.
This occures often when you package as an admin and the sid ends up with 500.
The new system will recognise it and import the sid as all users, and that makes the profiles often corrupt.
I hope this helps you.
Regards
Erik
www.DinamiQs.com
Dinamiqs is the home of VirtualStorm (www.virtualstorm.org)
If Erik's solution doesn't
If Erik's solution doesn't resolve the issue create an empty layer on a machine (no importing just create a new one with nothing in it), set it to activate on system startup and see if this happens.
If a forum post solves your problem please flag is as the solution
I you like an article, blog post or download vote it up
Would you like to reply?
Login or Register to post your comment.