The Workaround: Removing Windows PIN and Credential Manager

Here's how you can tackle that email and password request issue without Intune:

Step 1: Remove Windows PIN - Check out this handy guide for step-by-step instructions on getting rid of the Windows PIN.

• You might have noticed that the 'Remove' option for the Windows PIN can be a bit elusive. That's because Azure AD integration plays hide-and-seek with this feature. By ditching the PIN, you simplify the whole authentication process.

Step 2: Using CMD or PowerShell to Add Credentials

To make life easier when accessing network shares without Intune, you can roll up your sleeves and use Command Prompt (CMD) or PowerShell to feed your Windows Credential Manager with the necessary credentials. This ensures you can breeze through network resource access without email and password requests bugging you.

Using Command Prompt (CMD):

1. Open Command Prompt as an administrator.
2. Type the following command and press Enter:

   
   cmdkey /add:192.168.1.100 /user:JohnDoe /pass:YourPassword123 
   

3. Replace 192.168.1.100 with the IP address of the server or network resource you want to access.
4. Replace JohnDoe with your username for that resource.
5. Replace YourPassword123 with your password for that resource.

Using PowerShell:

1. Open PowerShell as an administrator.
2. Use the following commands to create a credential object and add it to the Windows Credential Manager:

   
   $username = "JohnDoe"
   $password = ConvertTo-SecureString -String "YourPassword123" -AsPlainText -Force
   $credential = New-Object System.Management.Automation.PSCredential($username, $password)
   # Add the credential to the Windows Credential Manager
   cmdkey /add:192.168.1.100 /user:$($credential.UserName) /pass:$($credential.GetNetworkCredential().Password)
   
   

3. Replace 192.168.1.100 with the IP address of the server or network resource you want to access.
4. Replace JohnDoe with your username for that resource.
5. Replace YourPassword123 with your password for that resource.

By following these steps and using the provided examples, you can keep your network resource access smooth and hassle-free, even without the superpowers of Intune.

The Alternative Workaround: Creating a New Local User

If you're up for an alternative workaround, you can opt for this route:

Step 1: Create a New Local User Account

• Go to "Settings" > "Accounts" > "Family & other users."
• Under "Other users," select "Add someone else to this PC."
• Choose "I don't have this person's sign-in information."
• Select "Add a user without a Microsoft account."
• Enter the username and password for your new local user account, making sure to set them as an administrator. Follow the on-screen instructions to complete the setup.

Step 2: Migrate Your Files and Settings

• Once the new local user account is good to go, it's time to transfer your files and settings from your current profile to the new one. This includes documents, pictures, and any other data you want to keep.
• You'll also need to set up your applications and preferences again within the new user account.

Step 3: Log in as the New Local User

• After setting up the new local user account, log in using these credentials. Since this user isn't connected to Azure AD, you won't run into those pesky email and password requests when accessing network shares.

This alternative workaround provides a fresh start by creating a new local user account and migrating your data and settings. It's a solid choice for those who want to sidestep the Azure AD integration challenges. Keep in mind that it involves some effort in transferring your files and reconfiguring your applications and preferences.

And there you have it!