In the folder where you ran analysis, at the command prompt, type notepad usermap.xml, and then press Enter.

The following XML file appears:

<?xml version="1.0" encoding="utf-8"?>
<UserMappings>
<UserMap From="Admin" To=""></UserMap>
<UserMap From="guest" To=""></UserMap> 
<UserMap From="Jane" To=""></UserMap>
<UserMap From="Mike" To=""></UserMap>
</UserMappings>

For each Visual SourceSafe username you want to map, add a valid Windows user name or Team Foundation Server user name in ‘To’ field, as shown in this example:

<?xml version="1.0" encoding="utf-8"?>
<UserMappings>
<UserMap From="Admin" To="MYDOMAIN\Jennifer"></UserMap>
<UserMap From="guest" To="TestAlias1"></UserMap> 
<UserMap From="Jane" To="Jane"></UserMap>
<UserMap From="Mike" To=""></UserMap>
</UserMappings>

If you provide a user name mapping similar to <UserMap From="Mike" To=""></UserMap> where "Mike" is a valid Windows user name, Team Foundation maps "Mike" to "MYDOMAIN\Mike," where MYDOMAIN is the default domain. If you provide no mapping for valid Windows user "Mike", Team Foundation also maps "Mike" to "MYDOMAIN\Mike." However if "Mike" is not a valid user then Team Foundation maps "Mike" to "Mike," and "Mike" is not a valid user in Team Foundation.

Tip:
Assign the Visual SourceSafe "guest" account to a Windows user account or Team Foundation user, if you can, to avoid losing a record of versioning actions performed on behalf of the guest user.

Save your changes and close Notepad.