The fastest way to find out if you've migrated is to look at the first login screen.

If you see a "Sign in to: AD" message below the credentials field, congratulations! Your computer has been migrated already.

Another way is after you've already logged in. Launch the "About your PC" utility by searching for "About" in the Taskbar, or by using the "Windows Key + Pause/Break" shortcut to quickly launch it.

This menu will show the specifications for your computer as well as your Device name. If you are migrated already, the Full device name field will show your computer name followed by ad.wisc.edu, as shown below. 

Note: If you have multiple computers, they will all need to be migrated individually. Please verify that all of the computers you work on have been migrated.

Please make sure you are using your UW-Madison NetID and password and that you see a "Sign in to: AD" message below the credentials field (see above).

Assuming that those credentials are correct, the most likely explanation is that the computer has not successfully joined the ad.wisc.edu domain. This can be verified if you don't see the "Sign in to: AD" message below the credentials field:

There are many different ways this can happen, but the most common is that there was an issue during imaging or the migration script.

Recommendations to fix:

• Contact User Support Services to get this issue corrected. Your computer will need to be joined to AD manually by one of our technicians.

The most likely explanation is that you do not have a connection to the internal network. Please see this article for help with mapping network drives:

Working Remotely - Network Drive Access

If you have been through the article already and need further assistance, please contact User Support Services

Note: If you have verified your network connection, and you see your network drives in Windows Explorer under This PC, but they have "X" symbols through them, double-clicking on the drive will allow you to browse the drive. The X indicator does not automatically go away when your connection is restored.

 

The letters for your drive mappings should be the same before your migration and after. Some of the labels for those network drives may have changed.

           

The actual file paths remain unchanged. For example F:\WORK_GRP\Common is still in the same place.

In some cases, your access may have been inadvertently lost but it can be corrected.

IIT Staff are auditing and adjusting permissions as we switch everyone to using their UW Madison NetID for computer logins. In some cases, file system access for the old Surgery username was restricted to only a few folders. This type of access isn't always captured or known since our folder structure is massive. We rely on emails to User Support Services to let us know when there's a problem so that we can restore access on the UW Madison side.

If you notice any other permissions issues, please don't hesitate to get in touch with User Support Services so that the ticket can get escalated to the infrastructure group and resolved.

This is a change that is usually done as part of the migration process; however, it is easy to miss. Sorry about that!

Recommendations to fix:

• Contact User Support Services to get this issue corrected. Your computer will need to be moved to another AD container manually by one of our technicians.

There are a few different ways this can happen, but the most common is that there was an issue during the migration script.

Recommendations to fix:

• Contact User Support Services to get this issue corrected. Your desktop items can be copied, but it will need to be done manually by one of our technicians.

This is a normal part of the setup process and typical for these programs. Once you login to those services, it shouldn't ask again for a while.

Enter your NetID credentials on the UW-Madison Login (SSO - Single Sign On) page.

Note: You may also be prompted for MFA/DUO authentication.

The cause of this prompt is because the migration process renamed your local profile to your NetID. The program needs your login credentials again as a result.