

- #NETWORK FILE SHARING USING USER ACCOUNTS UPDATE#
- #NETWORK FILE SHARING USING USER ACCOUNTS WINDOWS 10#
- #NETWORK FILE SHARING USING USER ACCOUNTS PROFESSIONAL#
For me, I started as a music teacher in 1989. Especially since many of us here predate there even BEING IT as we know it. This is an "interesting ways we ended up in IT" thing.
#NETWORK FILE SHARING USING USER ACCOUNTS PROFESSIONAL#
Misconception.I spent most of my professional journey kicking shadows. Misconceptions about the IT journey - what is your story? IT & Tech Careers.Im really embarrassed saying this but we have things setup so in order for people to reset their 365 passwords they need to call somebody in IT so we can do it in Active Directory Users and Computers and then synchronize it with the sync tool for 365.Is i. Let people reset their own passwords Cloud Computing & SaaS.
#NETWORK FILE SHARING USING USER ACCOUNTS UPDATE#
Windows 10's 21H2 feature update is now available for all users and it looks to heavily focus on security.
#NETWORK FILE SHARING USING USER ACCOUNTS WINDOWS 10#
Windows 10 21H2 now in broad deployment, available to everyone

No changes have been made that would result in this behavior on the network or systems side. Deleting the user account and recreating the account (after deleting the user profile folder, the registry entry in ProfileList, and the user itself) results in the same symptoms. I have just resorted to asking users for passwords.

Unfortunately this is preventing our move to cloud folders. There is no way we can get a path for User A that is the same as User B. A simple example is a folder path for an excel macro. Creating a new user account with a different name results in being able to access the share. The issue is a lot of our core files need sharable location paths. This issue is occurring on every computer with this particular local account (including computers attached to the domain, signing in locally). The server is pingable, and the share is not reachable using FQDN or IP address. I don't think it's a permissions issue as it's a local account and it's not even attempting to authenticate with a username and password. Clicking on the shared folder results in a "Windows cannot access \\server\share" and says we don't have permissions. It doesn't ask for credentials at all, instead shows the shared volume in Windows Explorer. When logged in to this local account and attempting to access a network share, the network share doesn't attempt to authenticate. We have a local account set up on many of our (non-domain) computers. Here's a head scratcher for you experts out there:
