DOCSLIB.ORG

[MS-EFSR]: Encrypting File System Remote (EFSRPC) Protocol

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

[MS-EFSR]: Encrypting File System Remote (EFSRPC) Protocol Intellectual Property Rights Notice for Open Specifications Documentation . Technical Documentation. Microsoft publishes Open Specifications documentation (“this documentation”) for protocols, file formats, data portability, computer languages, and standards support. Additionally, overview documents cover inter-protocol relationships and interactions. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you can make copies of it in order to develop implementations of the technologies that are described in this documentation and can distribute portions of it in your implementations that use these technologies or in your documentation as necessary to properly document the implementation. You can also distribute in your implementation, with or without modification, any schemas, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications documentation. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that might cover your implementations of the technologies described in the Open Specifications documentation. Neither this notice nor Microsoft's delivery of this documentation grants any licenses under those patents or any other Microsoft patents. However, a given Open Specifications document might be covered by the Microsoft Open Specifications Promise or the Microsoft Community Promise. If you would prefer a written license, or if the technologies described in this documentation are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected]. License Programs. To see all of the protocols in scope under a specific license program and the associated patents, visit the Patent Map. Trademarks. The names of companies and products contained in this documentation might be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit www.microsoft.com/trademarks. Fictitious Names. The example companies, organizations, products, domain names, email addresses, logos, people, places, and events that are depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred. Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than as specifically described above, whether by implication, estoppel, or otherwise. Tools. The Open Specifications documentation does not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments, you are free to take advantage of them. Certain Open Specifications documents are intended for use in conjunction with publicly available standards specifications and network programming art and, as such, assume that the reader either is familiar with the aforementioned material or has immediate access to it. Support. For questions and support, please contact [email protected]. 1 / 92 [MS-EFSR] - v20210625 Encrypting File System Remote (EFSRPC) Protocol Copyright © 2021 Microsoft Corporation Release: June 25, 2021 Revision Summary Revision Revision Date History Class Comments 3/2/2007 1.0 New Version 1.0 release 4/3/2007 1.1 Minor Version 1.1 release 5/11/2007 1.2 Minor Version 1.2 release 6/1/2007 1.2.1 Editorial Changed language and formatting in the technical content. 7/3/2007 1.3 Minor Clarified the meaning of the technical content. 8/10/2007 2.0 Major Updated and revised the technical content. 9/28/2007 3.0 Major Converted to unified format. 10/23/2007 3.1 Minor Clarified the meaning of the technical content. 1/25/2008 3.1.1 Editorial Changed language and formatting in the technical content. 3/14/2008 3.1.2 Editorial Changed language and formatting in the technical content. 6/20/2008 4.0 Major Updated and revised the technical content. 7/25/2008 4.0.1 Editorial Changed language and formatting in the technical content. 8/29/2008 4.0.2 Editorial Changed language and formatting in the technical content. 10/24/2008 4.0.3 Editorial Changed language and formatting in the technical content. 12/5/2008 5.0 Major Updated and revised the technical content. 1/16/2009 5.0.1 Editorial Changed language and formatting in the technical content. 2/27/2009 5.0.2 Editorial Changed language and formatting in the technical content. 4/10/2009 5.0.3 Editorial Changed language and formatting in the technical content. 5/22/2009 6.0 Major Updated and revised the technical content. 7/2/2009 6.0.1 Editorial Changed language and formatting in the technical content. 8/14/2009 6.0.2 Editorial Changed language and formatting in the technical content. 9/25/2009 7.0 Major Updated and revised the technical content. 11/6/2009 8.0 Major Updated and revised the technical content. 12/18/2009 9.0 Major Updated and revised the technical content. 1/29/2010 10.0 Major Updated and revised the technical content. 3/12/2010 11.0 Major Updated and revised the technical content. 4/23/2010 11.0.1 Editorial Changed language and formatting in the technical content. 6/4/2010 12.0 Major Updated and revised the technical content. 7/16/2010 13.0 Major Updated and revised the technical content. 8/27/2010 14.0 Major Updated and revised the technical content. 2 / 92 [MS-EFSR] - v20210625 Encrypting File System Remote (EFSRPC) Protocol Copyright © 2021 Microsoft Corporation Release: June 25, 2021 Revision Revision Date History Class Comments 10/8/2010 15.0 Major Updated and revised the technical content. No changes to the meaning, language, or formatting of the 11/19/2010 15.0 None technical content. No changes to the meaning, language, or formatting of the 1/7/2011 15.0 None technical content. 2/11/2011 16.0 Major Updated and revised the technical content. 3/25/2011 17.0 Major Updated and revised the technical content. No changes to the meaning, language, or formatting of the 5/6/2011 17.0 None technical content. 6/17/2011 17.1 Minor Clarified the meaning of the technical content. 9/23/2011 18.0 Major Updated and revised the technical content. 12/16/2011 19.0 Major Updated and revised the technical content. No changes to the meaning, language, or formatting of the 3/30/2012 19.0 None technical content. No changes to the meaning, language, or formatting of the 7/12/2012 19.0 None technical content. 10/25/2012 20.0 Major Updated and revised the technical content. No changes to the meaning, language, or formatting of the 1/31/2013 20.0 None technical content. 8/8/2013 21.0 Major Updated and revised the technical content. No changes to the meaning, language, or formatting of the 11/14/2013 21.0 None technical content. No changes to the meaning, language, or formatting of the 2/13/2014 21.0 None technical content. No changes to the meaning, language, or formatting of the 5/15/2014 21.0 None technical content. 6/30/2015 22.0 Major Significantly changed the technical content. 10/16/2015 23.0 Major Significantly changed the technical content. 7/14/2016 24.0 Major Significantly changed the technical content. No changes to the meaning, language, or formatting of the 6/1/2017 24.0 None technical content. 9/15/2017 25.0 Major Significantly changed the technical content. No changes to the meaning, language, or formatting of the 12/1/2017 25.0 None technical content. 9/12/2018 26.0 Major Significantly changed the technical content. 4/7/2021 27.0 Major Significantly changed the technical content. 6/25/2021 28.0 Major Significantly changed the technical content. 3 / 92 [MS-EFSR] - v20210625 Encrypting File System Remote (EFSRPC) Protocol Copyright © 2021 Microsoft Corporation Release: June 25, 2021 Table of Contents 1 Introduction ............................................................................................................ 6 1.1 Glossary ........................................................................................................... 6 1.2 References ...................................................................................................... 10 1.2.1 Normative References ................................................................................. 11 1.2.2 Informative References ............................................................................... 11 1.3 Overview ........................................................................................................ 12 1.4 Relationship to Other Protocols .......................................................................... 16 1.5 Prerequisites/Preconditions ............................................................................... 17 1.6 Applicability Statement ..................................................................................... 17 1.7 Versioning and Capability Negotiation ................................................................. 17 1.8 Vendor-Extensible Fields ................................................................................... 18 1.9 Standards Assignments ..................................................................................... 18 2 Messages ..............................................................................................................
Recommended publications
  • NTFS • Windows Reinstallation – Bypass ACL • Administrators Privilege – Bypass Ownership

    NTFS • Windows Reinstallation – Bypass ACL • Administrators Privilege – Bypass Ownership

    Windows Encrypting File System Motivation • Laptops are very integrated in enterprises… • Stolen/lost computers loaded with confidential/business data • Data Privacy Issues • Offline Access – Bypass NTFS • Windows reinstallation – Bypass ACL • Administrators privilege – Bypass Ownership www.winitor.com 01 March 2010 Windows Encrypting File System Mechanism • Principle • A random - unique - symmetric key encrypts the data • An asymmetric key encrypts the symmetric key used to encrypt the data • Combination of two algorithms • Use their strengths • Minimize their weaknesses • Results • Increased performance • Increased security Asymetric Symetric Data www.winitor.com 01 March 2010 Windows Encrypting File System Characteristics • Confortable • Applying encryption is just a matter of assigning a file attribute www.winitor.com 01 March 2010 Windows Encrypting File System Characteristics • Transparent • Integrated into the operating system • Transparent to (valid) users/applications Application Win32 Crypto Engine NTFS EFS &.[ßl}d.,*.c§4 $5%2=h#<.. www.winitor.com 01 March 2010 Windows Encrypting File System Characteristics • Flexible • Supported at different scopes • File, Directory, Drive (Vista?) • Files can be shared between any number of users • Files can be stored anywhere • local, remote, WebDav • Files can be offline • Secure • Encryption and Decryption occur in kernel mode • Keys are never paged • Usage of standardized cryptography services www.winitor.com 01 March 2010 Windows Encrypting File System Availibility • At the GUI, the availibility
  • Active @ UNDELETE Users Guide | TOC | 2

    Active @ UNDELETE Users Guide | TOC | 2

    Active @ UNDELETE Users Guide | TOC | 2 Contents Legal Statement..................................................................................................4 Active@ UNDELETE Overview............................................................................. 5 Getting Started with Active@ UNDELETE........................................................... 6 Active@ UNDELETE Views And Windows......................................................................................6 Recovery Explorer View.................................................................................................... 7 Logical Drive Scan Result View.......................................................................................... 7 Physical Device Scan View................................................................................................ 8 Search Results View........................................................................................................10 Application Log...............................................................................................................11 Welcome View................................................................................................................11 Using Active@ UNDELETE Overview................................................................. 13 Recover deleted Files and Folders.............................................................................................. 14 Scan a Volume (Logical Drive) for deleted files..................................................................15
  • Softnas Deployment Guide for High- Performance SQL Storage

    Softnas Deployment Guide for High- Performance SQL Storage

    SoftNAS Deployment Guide for High- Performance SQL Storage Introduction SoftNAS cloud NAS systems are based on an innovative, memory-centric storage architecture that delivers unparalleled NAS performance, efficiency, and value. They incorporate a hybrid disk storage technology that tailors the usage of data disks, log solid- state cache drives (SSDs), and read cache SSDs to the data share's specific needs. Additional features include variable storage record size, data compression, and multiple connectivity options. As a Cloud NAS solution, SoftNAS cloud NAS systems provide an excellent base for Microsoft Windows Server deployments by providing iSCSI or Fibre Channel block storage for Microsoft SQL Server, and network file system (NFS) or server message block (SMB) file storage for Microsoft Windows client access. This document covers the best practices to follow when deploying Microsoft SQL Server on a SoftNAS cloud NAS system. The intended audience is storage administrators and Microsoft SQL Server database administrators. Maintaining High Availability As with any business-critical application, high availability is a crucial design criterion to be considered when deploying a Microsoft SQL Server installation. Microsoft SQL Server 2016 can be installed on local and/or shared file systems, and SoftNAS cloud NAS systems can satisfy both of these options. Local file systems (from the Microsoft Windows Server perspective) are hosted as block volumes—iSCSI and/or Fibre-Channel-connected LUNs and file systems as SMB and/or NFS volumes. High availability starts with the network connectivity supporting the storage and server interconnectivity. Any design for the storage infrastructure should avoid single points of failure. Because many white papers and publications cover storage-area networking and network-attached storage resilience, those topics are not covered in detail in this paper.
  • Comptia A+ Acronym List Core 1 (220-1001) and Core 2 (220-1002)

    Comptia A+ Acronym List Core 1 (220-1001) and Core 2 (220-1002)

    CompTIA A+ Acronym List Core 1 (220-1001) and Core 2 (220-1002) AC: Alternating Current ACL: Access Control List ACPI: Advanced Configuration Power Interface ADF: Automatic Document Feeder ADSL: Asymmetrical Digital Subscriber Line AES: Advanced Encryption Standard AHCI: Advanced Host Controller Interface AP: Access Point APIPA: Automatic Private Internet Protocol Addressing APM: Advanced Power Management ARP: Address Resolution Protocol ASR: Automated System Recovery ATA: Advanced Technology Attachment ATAPI: Advanced Technology Attachment Packet Interface ATM: Asynchronous Transfer Mode ATX: Advanced Technology Extended AUP: Acceptable Use Policy A/V: Audio Video BD-R: Blu-ray Disc Recordable BIOS: Basic Input/Output System BD-RE: Blu-ray Disc Rewritable BNC: Bayonet-Neill-Concelman BSOD: Blue Screen of Death 1 BYOD: Bring Your Own Device CAD: Computer-Aided Design CAPTCHA: Completely Automated Public Turing test to tell Computers and Humans Apart CD: Compact Disc CD-ROM: Compact Disc-Read-Only Memory CD-RW: Compact Disc-Rewritable CDFS: Compact Disc File System CERT: Computer Emergency Response Team CFS: Central File System, Common File System, or Command File System CGA: Computer Graphics and Applications CIDR: Classless Inter-Domain Routing CIFS: Common Internet File System CMOS: Complementary Metal-Oxide Semiconductor CNR: Communications and Networking Riser COMx: Communication port (x = port number) CPU: Central Processing Unit CRT: Cathode-Ray Tube DaaS: Data as a Service DAC: Discretionary Access Control DB-25: Serial Communications
  • Copyrighted Material

    Copyrighted Material

    Index Note to the Reader: Throughout this index boldfaced page numbers indicate primary discussions of a topic. Italicized page numbers indicate illustrations. IUSR_computername account, 274–275 Numbers disabling, 61 mapping certificates to, 283–286 3DES, 125–126, 416, 494 user accounts, configuring for 802.1x standard (IEEE), 181–184, 494 delegation, 46 authentication for, 182 ACEs (Access Control Entries) combining VPNs with, 190 authentication for clients, 494 802.11a standard (IEEE), 494 in Discretionary Access Control List, 7 vs. 802.11b, 170 Active Directory (AD), 3, 494 802.11b standard (IEEE), 494 assigning GPO to container in, 28 for certificate store, 404 Configuration container for certificate templates, 360 A mapping certificates to accounts, 283–286 Access Control Entries (ACEs), 494 in mixed mode, 324 in Discretionary Access Control List, 7 publishing certificates through, 404–409 Access Control List (ACL), 494 in child domain, 406–409 Access Control Settings dialog box, 16 from standalone online CA, 404–406 Auditing tab, 16, 440 to view published certificates and CRLs, “Access Is Denied” error message, 420 358–359 access point, 494. See also wireless access Active Directory domain controller point (WAP) client security to traffic, 226–229 access token, 260, 494 testing, 227–229 account lockout policy, in security Active Directory domains templates, 9 Properties dialog box, General tab, 228 account logon events, tracking, 15, 445 trust relationships, 271–273, 272 account management events, tracking, 15, Active Directory object, auditing, 18 445–446 Active Directory Properties dialog box, 228 Account Policies Active Directory Sites and Services (ADSS), security template configuration, 12, 5, 494 12–14, 13 configuration, 407–408 in security templates, 9 Active Directory Users and Computers (ADUC), accountability trail, 14 COPYRIGHTED5, MATERIAL494 accounts Active Server Pages (ASP), SUS and, 111 Administrator account, renaming, 55, 56 AD.
  • Jim Allchin on Longhorn, Winfs, 64-Bit and Beyond Page 34 Jim

    Jim Allchin on Longhorn, Winfs, 64-Bit and Beyond Page 34 Jim

    0805red_cover.v5 7/19/05 2:57 PM Page 1 4 Scripting Solutions to Simplify Your Life Page 28 AUGUST 2005 WWW.REDMONDMAG.COM MrMr WindowsWindows Jim Allchin on Longhorn, WinFS, 64-Bit and Beyond Page 34 > $5.95 05 • AUGUST Make Room for Linux Apps Page 43 25274 867 27 Active Directory Design Disasters Page 49 71 Project1 6/16/05 12:36 PM Page 1 Exchange Server stores & PSTs driving you crazy? Only $399 for 50 mailboxes; $1499 for unlimited mailboxes! Archive all mail to SQL and save 80% storage space! Email archiving solution for internal and external email Download your FREE trial from www.gfi.com/rma Project1 6/16/05 12:37 PM Page 2 Get your FREE trial version of GFI MailArchiver for Exchange today! GFI MailArchiver for Exchange is an easy-to-use email archiving solution that enables you to archive all internal and external mail into a single SQL database. Now you can provide users with easy, centralized access to past email via a web-based search interface and easily fulfill regulatory requirements (such as the Sarbanes-Oxley Act). GFI MailArchiver leverages the journaling feature of Exchange Server 2000/2003, providing unparalleled scalability and reliability at a competitive cost. GFI MailArchiver for Exchange features Provide end-users with a single web-based location in which to search all their past email Increase Exchange performance and ease backup and restoration End PST hell by storing email in SQL format Significantly reduce storage requirements for email by up to 80% Comply with Sarbanes-Oxley, SEC and other regulations.
  • File Systems

    File Systems

    File Systems Profs. Bracy and Van Renesse based on slides by Prof. Sirer Storing Information • Applications could store information in the process address space • Why is this a bad idea? – Size is limited to size of virtual address space – The data is lost when the application terminates • Even when computer doesn’t crash! – Multiple process might want to access the same data File Systems • 3 criteria for long-term information storage: 1. Able to store very large amount of information 2. Information must survive the processes using it 3. Provide concurrent access to multiple processes • Solution: – Store information on disks in units called files – Files are persistent, only owner can delete it – Files are managed by the OS File Systems: How the OS manages files! File Naming • Motivation: Files abstract information stored on disk – You do not need to remember block, sector, … – We have human readable names • How does it work? – Process creates a file, and gives it a name • Other processes can access the file by that name – Naming conventions are OS dependent • Usually names as long as 255 characters is allowed • Windows names not case sensitive, UNIX family is File Extensions • Name divided into 2 parts: Name+Extension • On UNIX, extensions are not enforced by OS – Some applications might insist upon them • Think: .c, .h, .o, .s, etc. for C compiler • Windows attaches meaning to extensions – Tries to associate applications to file extensions File Access • Sequential access – read all bytes/records from the beginning – particularly convenient for magnetic tape • Random access – bytes/records read in any order – essential for database systems File Attributes • File-specific info maintained by the OS – File size, modification date, creation time, etc.
  • Encrypting File System

    Encrypting File System

    SVEUČILIŠTE U ZAGREBU FAKULTET ELEKTROTEHNIKE I RAČUNARSTVA Seminarski rad iz kolegija „Računalna forenzika“ Encrypting File System Luka Škorić Zagreb, siječanj, 2018. Sadržaj 1. Uvod ................................................................................................................................................ 1 2. NTFS............................................................................................................................................... 2 3. Karakteristike Encrypting File System-a ................................................................................... 4 3.1. Enkripcijski algoritmi ............................................................................................................. 5 3.2. Način rada .............................................................................................................................. 6 3.3. Nedostatci EFS-a .................................................................................................................. 8 4. Zaključak ...................................................................................................................................... 10 5. Literatura ...................................................................................................................................... 11 1. Uvod Enkripcija tvrdog diska predstavlja proces zaštite podataka pretvaranjem podataka u nečitki kod, što kao cilj ima zaštitu istih podataka od nedozvoljenog pristupa. Filesystem - level encryption, često nazvan i file/folder
  • SMB Remote File Protocol (Including SMB 3.X) Approved SNIA Tutorial © 2015 Storage Networking Industry Association

    SMB Remote File Protocol (Including SMB 3.X) Approved SNIA Tutorial © 2015 Storage Networking Industry Association

    SMBPRESENTATION remote TITLE file GOES protocol HERE (including SMB 3.x) Tom Talpey Microsoft SNIA Legal Notice The material contained in this tutorial is copyrighted by the SNIA unless otherwise noted. Member companies and individual members may use this material in presentations and literature under the following conditions: Any slide or slides used must be reproduced in their entirety without modification The SNIA must be acknowledged as the source of any material used in the body of any document containing material from these presentations. This presentation is a project of the SNIA Education Committee. Neither the author nor the presenter is an attorney and nothing in this presentation is intended to be, or should be construed as legal advice or an opinion of counsel. If you need legal advice or a legal opinion please contact your attorney. The information presented herein represents the author's personal opinion and current understanding of the relevant issues involved. The author, the presenter, and the SNIA do not assume any responsibility or liability for damages arising out of any reliance on or use of this information. NO WARRANTIES, EXPRESS OR IMPLIED. USE AT YOUR OWN RISK. SMB remote file protocol (including SMB 3.x) Approved SNIA Tutorial © 2015 Storage Networking Industry Association. All Rights Reserved. 2 Abstract and Learning Objectives Title: SMB remote file protocol (including SMB 3.x) Abstract The SMB protocol evolved over time from CIFS to SMB1 to SMB2, with implementations by dozens of vendors including most major Operating Systems and NAS solutions. The SMB 3.0 protocol had its first commercial implementations by Microsoft, NetApp and EMC by the end of 2012, and many other implementations exist or are in-progress.
  • Server Message Block in the Age of Microsoft Glasnost

    Server Message Block in the Age of Microsoft Glasnost

    Server Message Block in the Age of Microsoft Glasnost CHRISTOPHER R. HERTEL Christopher R. Hertel is a The EU anti-trust case against Microsoft concluded in late 2007 . Related or not, long-haul member of the that’s when things started to change . One pleasant surprise for third-party devel- Samba Team and co-founder opers was the release of hundreds of specifications covering Windows file formats, of the jCIFS project. He is also system internals, and protocols . Microsoft was opening up . Four years later, about the author of Implementing CIFS—The Common 400 specifications have been published . It took a while for some of those docu- Internet File System, the only developer’s guide ments to appear, mostly because Microsoft didn’t actually have them all written to the SMB/CIFS protocol suite. Not too long yet . And now they have surprised us again . Well before the beta release of Windows ago, he had the opportunity to work directly 8, they have provided preview documentation for an overhauled and compelling with Microsoft’s File Server team when the new version of the venerable Server Message Block Protocol: SMB2 .2 . This is going company he founded, ubiqx Consulting, to be epic . Inc., was tapped to write Microsoft’s official SMB/CIFS specifications. Chris has also A Gathering of Storage Geeks been adjunct faculty at the University of Once a year, typically in September and typically somewhere near San Jose, Minnesota College of Continuing Education California, the Storage Networking Industry Association (SNIA) hosts the Stor- (CCE) and is currently a member of the CCE IT age Developer Conference (SDC) .
  • Windows Poster 20-12-2013 V3

    Windows Poster 20-12-2013 V3

    Microsoft® Discover the Open Specifications technical documents you need for your interoperability solutions. To obtain these technical documents, go to the Open Specifications Interactive Tiles: open specifications poster © 2012-2014 Microsoft Corporation. All rights reserved. http://msdn.microsoft.com/openspecifications/jj128107 Component Object Model (COM+) Technical Documentation Technical Documentation Presentation Layer Services Technical Documentation Component Object Model Plus (COM+) Event System Protocol Active Directory Protocols Overview Open Data Protocol (OData) Transport Layer Security (TLS) Profile Windows System Overview Component Object Model Plus (COM+) Protocol Active Directory Lightweight Directory Services Schema WCF-Based Encrypted Server Administration and Notification Protocol Session Layer Services Windows Protocols Overview Component Object Model Plus (COM+) Queued Components Protocol Active Directory Schema Attributes A-L Distributed Component Object Model (DCOM) Remote Protocol Windows Overview Application Component Object Model Plus (COM+) Remote Administration Protocol Directory Active Directory Schema Attributes M General HomeGroup Protocol Supplemental Shared Abstract Data Model Elements Component Object Model Plus (COM+) Tracker Service Protocol Active Directory Schema Attributes N-Z Peer Name Resolution Protocol (PNRP) Version 4.0 Windows Data Types Services General Application Services Services Active Directory Schema Classes Services Peer-to-Peer Graphing Protocol Documents Windows Error Codes ASP.NET
  • Disk Management (4 Min) When We Want to Install a Hard Drive in Our System We're Going to Need to Make That Hard Drive Either a Basic Disk Or a Dynamic Disk

    Disk Management (4 Min) When We Want to Install a Hard Drive in Our System We're Going to Need to Make That Hard Drive Either a Basic Disk Or a Dynamic Disk

    Video – Disk Management (4 min) When we want to install a hard drive in our system we're going to need to make that hard drive either a basic disk or a dynamic disk. A basic disk, which is the default, contains primary and extended partitions as well as logical drives. A basic disk is limited to four partitions. The Windows operating system needs to be installed onto a basic disk. After it's installed the basic disk can then be converted to a dynamic disk. Primary partition. The primary partition contains the operating system. There can be up to four primary partitions per hard drive and a primary partition cannot be subdivided into smaller sections. A primary partition can also be marked as the active partition. The operating system uses the active partition to boot the computer. Only one primary partition per disk can be marked as active. In most cases, the C: drive is the active partition and contains the boot and system files. Meaning the MBR or Master Boot Record Partition Table. Newer systems that use EFI instead of BIOS are using the GPT or GUID partition table. If you're using the GPT instead of the MBR partition table you can have more than four primary partitions on a disk. An extended partition. There can only be one extended partition per hard drive. Once again, primary partitions, active partitions and extended partitions are all part of a basic disk. An extended partition cannot hold the operating system, but it can be subdivided into smaller sections called logical drives.