Joe Smith's questions

Elaboration:

I migrated the storage of some people's roaming profile from one Windows Server to another, and updated the profile location through Active Directory to reflect the change. Now for everyone I've done this to I'm seeing the notification on these users:

There was a problem with your roaming profile you have been logged on with your previously saved local profile. Please see the event log for details or contact your administrators.

After looking through the local machine's Event Viewer, I'm seeing Event ID 1521 with the description:

Windows cannot locate the server copy of your roaming profile and is attempting to log you on with your local profile. Changes to the profile will not be copied to the server when you log off. This error may be caused by network problems or insufficient security rights.

DETAIL - The process cannot access the file because it is being used by another process.

I configured the share and permissions to match what is listed here, and I can confirm access by navigating to \\servername\profileshare$\userprofile.V6, and being able to access the contents of the user profile (and only that user profile) perfectly fine.

The server in question doesn't have anything special installed (ie an Antivirus), so I'm wondering if someone could help me figure out what 'other process' Event Viewer is talking about, and to solve the problem.

Update: This error doesn't appear to be consistent - sometimes I can sign in without problems, but more often than not I get the message described above.

I initially deployed Python 3.8.1 in our org (through WSUS Package Publisher if relevant) using the MSI's found here. I installed these MSI's using WSUS Package Publisher with the following command for each MSI:

msiexec.exe /i core.msi /qn /norestart ALLUSERS=1

Unfortunately for some reason this was causing a number of issues for me which all seemed to point to the ALLUSERS=1 being ignored, possibly due to lack of elevation of the installer (not appearing in the Installed Applications list, not appearing through the py -0 list). Frustratingly these were all accidentally deployed to everyone before we realised these issues.

To clean up, I now need to uninstall these MSI's. Right clicking these MSI's on the affected machine and clicking "Uninstall" works - I get presented a "Are you sure you want to uninstall?" prompt, followed by elevation request, and then it uninstalls as expected.

However, as I'm trying to do this silently so that I can roll this out. This is the command I'm trying to run through an elevated shell:

 msiexec.exe /x .\core.msi /qn

Nothing happens. I can see in Task Manager that msiexec.exe is running with no activity, so my feeling is that it's reaching the "Are you sure?" prompt and getting stuck on that prompt.

How do I bypass this prompt during silent uninstallation?