What are we learning?
Explain how file permissions and share permissions control access to shared files.
Lesson 3.2 · Opening
Explain how file permissions and share permissions control access to shared files.
I can independently demonstrate read-only and editing access to the shared folder, map it correctly, and explain the permission difference using evidence.
I can distinguish share access from NTFS file access.
I can prove the intended user can read or edit the practice file.
I can map the share and explain its ownership.
Touch, mouse, or keyboard. No grades or saved progress. Optional timer and temporary game points in Describe It!
Practice at your own pace. No grades or saved results.
Use two assigned guests with distinct names, guest rights and recovery. Verify the approved router-LAN or bridged classroom route before students begin. Separate NAT adapters are not a shared guest LAN; an Internal Network name joins only VMs on the same physical host. Bridged peers need school-network permission. Preserve authentication, signing and firewall protections. Do not use the dedicated sharing identity as an administrator or folder owner. Before removing broad groups, preserve explicit Full control for the signed-in working host user as well as the existing owner, SYSTEM and Administrators; an owner group alone may be filtered from ordinary Explorer access. Confirm ShareReader effective Read is not defeated by inherited/group write rights. No private password appears in the handout.
Practice guests only. Change only the new named folder/share and dedicated lab identity. Never share C:, a whole profile or real personal files. Do not disable the firewall, SMB signing or password protection, enable insecure Guest/SMB1, or change host networking. Stop on an unexpected permission, identity or network state.
Original teaching for IT Specialist Device Configuration and Management objective 3.2.
Introductory access-control reasoning; not a compliance assessment.
Expose identity, layers and mapping misconceptions.
Predict outcomes and examine feedback.
Can learners distinguish an access grant from a convenient path?
Explain general access-control concepts and trade-offs.
Reason through original cases.
Can learners identify the actual limiting layer?
Verify assigned endpoints and support bounded guest-only configuration.
Configure, test, capture in flow and disconnect the temporary share mapping.
Does each learner have their own actual remote evidence?
Security principals, NTFS permissions, inheritance and ownership.
Windows 11 Explorer routes. This lab retains password-protected sharing and existing security controls.
Requested rights, applicable entries and access-check ordering; not a universal most-restrictive rule within an ACL.
Distinguish explicit entries from inherited entries and their ordering.
Create files/Write data has different meanings for a directory and a file.
Use authenticated sharing; do not disable signing or enable insecure Guest access.
Authorized recovery; changing ownership does not itself grant ordinary file-content access.
NAT, Internal Network and bridged networking have different reachability boundaries.
Continue can permanently change a folder ACL. Preserve the authorized working host user explicitly on this new practice folder; do not use a surprise Continue prompt to repair unrelated data.
Ordinary Explorer uses the standard token. Administrator membership is not the same as an explicit ordinary folder-access grant.
Illustrated real-VM guide and evidence worksheet. Instructor and document accessibility review remain required.
12 visual slides · Explore at your own pace
A local path names a folder on this computer. A UNC path names a host and a share reached over the network.
Session only · Download to save · Submit your PDF through your class assignment system.
Fictional support ticket: a team needs a shared handover note. First let a coworker read it; then authorize editing. Prove both outcomes from a second Windows 11 guest.
Assigned guests only. Use a new empty practice folder, a dedicated non-administrator host account and a private nonblank password. Do not share drives/profiles, change host networking, disable protection, enable insecure Guest/SMB1, or take ownership of existing data. Stop if a named item already exists or you cannot identify the target.
Two different Windows guests let you prove actual remote access.
Add each screenshot at its capture step while the result is still open in your VM. Evidence & PDF lets you review those same images, add your name, download and submit externally. Download to save progress; closing this page loses the session.