There are several issues or conflicts that can occur in a roaming profile environment that basically come down to administrative questions.
Most items stored on the desktop or in the Start folder are shortcuts, so if the different PCs that the user is logging on from are not set up the exact same way (installed programs, folders, and so on), then the shortcuts might not be valid, and you might see a series of errors for invalid shortcuts when you log on in these situations.
Because most items stored on the desktop or in the Start folder are shortcuts, it is better not to mix and match different operating systems for the same user. Windows® 98 and Windows NT® profiles can co-exist in the same profile folder on the server. Because different types of information are stored in each case, you might see inconsistencies, particularly if the profiles are not mandatory.
If the same user is logged on to the same logon server from different clients, user profile information is saved independently during logoff for each logon. Therefore, the last client being logged off will reflect the actual changes saved to the profile.
You might receive a message that indicates that your roaming profile is not available. You will be logged on with your local profile. This typically means that the roaming profile might not be found in the expected place.
The error might also indicate that either the configured roaming profile folder is not shared or the integrated file system directory permissions do not allow access.
Users store files other than shortcuts on their desktop. If these files are large, it can significantly slow down the logon process. A workaround is to specify certain profile subfolders not to be included in the transfer between logon server and client.