Roaming profiles do not save when rebooting
Originally Published: 2000-07-07
Article Number
Applies To
Microsoft Windows NT 4.0
Network Access Protection (NAP)
Sub-Auth Protection (same as Network Access Protection)
Issue
When performing a shutdown or reboot, a user with a roaming profile on an NT domain protected by NAP (Sub-Auth) may be unable to save changes made to the roaming profile.
Cause
When performing a shutdown or restart, Windows NT does not allow such connections to be opened. After the shutdown procedure issues a stop to network services, no additional network connections can take place. If the roaming profile save does not occur before this, it will not be saved.
This by no means occurs on ALL domains. If the profile save request is issued BEFORE the network services are brought down, the save will occur normally.
This occurs in all versions of ACE/Agent using NAP.
Resolution
Related Articles
RSA SecurID Software Token 5.0.2 for Windows Desktop displays message after reboot due to roaming profile: No token stor… Number of Views Software Token for Windwos DeskTop, SWTDT v. 5.0.2 and later “No token storage device was detected" after reboot due to ro… Number of Views RSA SecurID Passage 3.5.1 unable to update roaming profile for Active Directory Domain User Number of Views Change the display pictures of the software token profiles on RSA Authentication Manager 8.x Security and Self-Service con… Number of Views 'Unable to save Connector' error when saving a JAVA Code Based AFX Connector in RSA Identity Governance & Lifecycle Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to set up the REST RSA SecurID Authentication API for Authentication Manager 8.2 SP1 RSA Authentication Manager 8.9 Known Issues
Don't see what you're looking for?
