{"id":12511,"date":"2011-10-03T00:01:00","date_gmt":"2011-10-03T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2011\/10\/03\/use-powershell-to-document-your-network-configuration\/"},"modified":"2011-10-03T00:01:00","modified_gmt":"2011-10-03T00:01:00","slug":"use-powershell-to-document-your-network-configuration","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/use-powershell-to-document-your-network-configuration\/","title":{"rendered":"Use PowerShell to Document Your Network Configuration"},"content":{"rendered":"

Summary:<\/strong> Learn how to use Windows PowerShell and Active Directory cmdlets to document your Active Directory configuration.<\/p>\n

 <\/p>\n

\"Hey,Hey, Scripting Guy! I recently inherited an Active Directory. By this, I mean the network administrator quit. He did not give any notice, and it appears he took any documentation he may have created with him. He may have been abducted by Martians (there seems to be quite a bit of this going on at work) for all I know. Anyway, I need a good way to easily discover information about the domain and the forest. If I could easily print it out, it would be even better. I know how to use Active Directory Users and Computers, and I have been making screen shots, but there should be a better way of doing things. Help!<\/p>\n

—BV<\/p>\n

 <\/p>\n

\"Hey,Hello BV,<\/p>\n

Microsoft Scripting Guy Ed Wilson here. I am sorry Martians abducted your network administrator. You did not specify which version of Windows you are running, and you did not say which version of domain controllers you have. I am guessing that perhaps you do not know. To find information about your operating system, you can use the following command in Windows PowerShell:<\/p>\n

Get-WmiObject win32_operatingsystem<\/p>\n

Using the Active Directory Windows PowerShell cmdlets and remoting, I can easily discover information about the forest and the domain. The first thing I need to do is to enter a PSSession<\/b> on the remote computer. To do this, I use the Enter-PSSession<\/b> cmdlet. Next, I import the active directory module, and set my working location to the root of the C drive. These commands are shown here:<\/p>\n

PS C:\\Users\\Administrator.NWTRADERS> Enter-PSSession dc1<\/p>\n

[dc1]: PS C:\\Users\\Administrator\\Documents> Import-Module activedirectory<\/p>\n

[dc1]: PS C:\\Users\\Administrator\\Documents> Set-Location c:\\<\/p>\n

After I have connected to the remote domain controller, I can use the Get-WmiObject<\/b> cmdlet to verify my operating system on that computer. This command and associated output are shown here:<\/p>\n

[dc1]: PS C:\\> Get-WmiObject win32_operatingsystem<\/p>\n

SystemDirectory : C:\\Windows\\system32<\/p>\n

Organization    :<\/p>\n

BuildNumber     : 7601<\/p>\n

RegisteredUser  : Windows User<\/p>\n

SerialNumber    : 55041-507-0212466-84005<\/p>\n

Version         : 6.1.7601<\/p>\n

Now, I want to get information about the forest. To do this, I use the Get-ADForrest<\/b> cmdlet. The output from Get-ADForest<\/b> includes lots of great information such as the domain naming master, forest mode, schema master, and domain controllers. This command and associated output are shown here:<\/p>\n

[dc1]: PS C:\\> Get-ADForest <\/p>\n

 <\/p>\n

ApplicationPartitions : {DC=DomainDnsZones,DC=nwtraders,DC=com, DC=ForestDnsZones,DC=nwtraders,DC=com}<\/p>\n

CrossForestReferences : {}<\/p>\n

DomainNamingMaster    : DC1.nwtraders.com<\/p>\n

Domains               : {nwtraders.com}<\/p>\n

ForestMode            : Windows2008Forest<\/p>\n

GlobalCatalogs        : {DC1.nwtraders.com}<\/p>\n

Name                  : nwtraders.com<\/p>\n

PartitionsContainer   : CN=Partitions,CN=Configuration,DC=nwtraders,DC=com<\/p>\n

RootDomain            : nwtraders.com<\/p>\n

SchemaMaster          : DC1.nwtraders.com<\/p>\n

Sites                 : {Default-First-Site-Name}<\/p>\n

SPNSuffixes           : {}<\/p>\n

UPNSuffixes           : {}<\/p>\n

The above commands and output are shown in the following figure.<\/p>\n

\"Image<\/a><\/p>\n

Now I am interested in obtaining information about the domain. To do this, I use the Get-ADDomain<\/b> cmdlet. The command returns important information such as the location of the default domain controller organizational unit, the PDC emulator, and the RID master. The command and associated output are shown here:<\/p>\n

[dc1]: PS C:\\> Get-ADDomain<\/p>\n

 <\/p>\n

AllowedDNSSuffixes                 : {}<\/p>\n

ChildDomains                       : {}<\/p>\n

ComputersContainer                 : CN=Computers,DC=nwtraders,DC=com<\/p>\n

DeletedObjectsContainer            : CN=Deleted Objects,DC=nwtraders,DC=com<\/p>\n

DistinguishedName                  : DC=nwtraders,DC=com<\/p>\n

DNSRoot                            : nwtraders.com<\/p>\n

DomainControllersContainer         : OU=Domain Controllers,DC=nwtraders,DC=com<\/p>\n

DomainMode                         : Windows2008Domain<\/p>\n

DomainSID                          : S-1-5-21-909705514-2746778377-2082649206<\/p>\n

ForeignSecurityPrincipalsContainer : CN=ForeignSecurityPrincipals,DC=nwtraders,DC=com<\/p>\n

Forest                             : nwtraders.com<\/p>\n

InfrastructureMaster               : DC1.nwtraders.com<\/p>\n

LastLogonReplicationInterval       :<\/p>\n

LinkedGroupPolicyObjects           : {CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=nwtraders,DC=com}<\/p>\n

LostAndFoundContainer              : CN=LostAndFound,DC=nwtraders,DC=com<\/p>\n

ManagedBy                          :<\/p>\n

Name                               : nwtraders<\/p>\n

NetBIOSName                        : NWTRADERS<\/p>\n

ObjectClass                        : domainDNS<\/p>\n

ObjectGUID                         : 0026d1fc-2e4d-4c35-96ce-b900e9d67e7c<\/p>\n

ParentDomain                       :<\/p>\n

PDCEmulator                        : DC1.nwtraders.com<\/p>\n

QuotasContainer                    : CN=NTDS Quotas,DC=nwtraders,DC=com<\/p>\n

ReadOnlyReplicaDirectoryServers    : {}<\/p>\n

ReplicaDirectoryServers            : {DC1.nwtraders.com}<\/p>\n

RIDMaster                          : DC1.nwtraders.com<\/p>\n

SubordinateReferences              : {DC=ForestDnsZones,DC=nwtraders,DC=com, DC=DomainDnsZones,DC=nwtraders,DC=com, CN=Configuration,DC=nwtraders,DC=com}<\/p>\n

SystemsContainer                   : CN=System,DC=nwtraders,DC=com<\/p>\n

UsersContainer                     : CN=Users,DC=nwtraders,DC=com<\/p>\n

From a security perspective, you should always check the domain password policy. To do this, use Get-ADDefaultDomainPasswordPolicy<\/b>. Things you want to especially pay attention to are the use of complex passwords, minimum password length, password age, and password retention. Of course, you also need to check lockout policy, too. This one is important to review closely when inheriting a new network. Here are the command and associated output:<\/p>\n

[dc1]: PS C:\\> Get-ADDefaultDomainPasswordPolicy<\/p>\n

 <\/p>\n

ComplexityEnabled           : True<\/p>\n

DistinguishedName           : DC=nwtraders,DC=com<\/p>\n

LockoutDuration             : 00:30:00<\/p>\n

LockoutObservationWindow    : 00:30:00<\/p>\n

LockoutThreshold            : 0<\/p>\n

MaxPasswordAge              : 42.00:00:00<\/p>\n

MinPasswordAge              : 1.00:00:00<\/p>\n

MinPasswordLength           : 7<\/p>\n

objectClass                 : {domainDNS}<\/p>\n

objectGuid                  : 0026d1fc-2e4d-4c35-96ce-b900e9d67e7c<\/p>\n

PasswordHistoryCount        : 24<\/p>\n

ReversibleEncryptionEnabled : False<\/p>\n

The last major thing to check is the domain controllers themselves. To do this, use the Get-ADDomainController<\/b> cmdlet. This command returns important information such as is the domain controller read-only, a global catalog server, operations master roles held, and operating system information. Here are the command and associated output:<\/p>\n

 [dc1]: PS C:\\> Get-ADDomainController -Identity dc1 <\/p>\n

 <\/p>\n

ComputerObjectDN           : CN=DC1,OU=Domain Controllers,DC=nwtraders,DC=com<\/p>\n

DefaultPartition           : DC=nwtraders,DC=com<\/p>\n

Domain                     : nwtraders.com<\/p>\n

Enabled                    : True<\/p>\n

Forest                     : nwtraders.com<\/p>\n

HostName                   : DC1.nwtraders.com<\/p>\n

InvocationId               : b51f625f-3f60-44e7-8577-8918f7396c2a<\/p>\n

IPv4Address                : 10.0.0.1<\/p>\n

IPv6Address                :<\/p>\n

IsGlobalCatalog            : True<\/p>\n

IsReadOnly                 : False<\/p>\n

LdapPort                   : 389<\/p>\n

Name                       : DC1<\/p>\n

NTDSSettingsObjectDN       : CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=nwtraders,DC=com<\/p>\n

OperatingSystem            : Windows Server 2008 R2 Enterprise<\/p>\n

OperatingSystemHotfix      :<\/p>\n

OperatingSystemServicePack : Service Pack 1<\/p>\n

OperatingSystemVersion     : 6.1 (7601)<\/p>\n

OperationMasterRoles       : {SchemaMaster, DomainNamingMaster, PDCEmulator, RIDMaster…}<\/p>\n

Partitions                 : {DC=ForestDnsZones,DC=nwtraders,DC=com, DC=DomainDnsZones,DC=nwtraders,DC=com, CN=Schema,CN=Configuration,DC=nwtraders,DC=com, CN=Configuration,DC=nwtraders,DC=com…}<\/p>\n

ServerObjectDN             : CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=nwtraders,DC=com<\/p>\n

ServerObjectGuid           : 5ae1fd0e-bc2f-42a7-af62-24377114e03d<\/p>\n

Site                       : Default-First-Site-Name<\/p>\n

SslPort                    : 636<\/p>\n

BV, you asked for a report. Now that we know what type of information to expect and how to obtain it, the report is as easy as redirecting the output to a text file. The associated commands are shown here.<\/p>\n

Get-ADForest >> \\\\dc1\\shared\\AD_Doc.txt<\/p>\n

Get-ADDomain >> \\\\dc1\\shared\\AD_Doc.txt<\/p>\n

Get-ADDefaultDomainPasswordPolicy >> \\\\dc1\\shared\\AD_Doc.txt<\/p>\n

Get-ADDomainController -Identity dc1 >>\\\\dc1\\shared\\AD_Doc.txt<\/p>\n

The file as viewed in Notepad is shown here.<\/p>\n

\"Image<\/a><\/p>\n

 <\/p>\n

Well, that is all there is to quickly documenting a new domain and forest. Join me tomorrow for the quick way to create and manipulate user objects in Active Directory.<\/p>\n

I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n

Ed Wilson, Microsoft Scripting Guy<\/b><\/p>\n

 <\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: Learn how to use Windows PowerShell and Active Directory cmdlets to document your Active Directory configuration.   Hey, Scripting Guy! I recently inherited an Active Directory. By this, I mean the network administrator quit. He did not give any notice, and it appears he took any documentation he may have created with him. He […]<\/p>\n","protected":false},"author":595,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[3,4,45],"class_list":["post-12511","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-scripting-guy","tag-scripting-techniques","tag-windows-powershell"],"acf":[],"blog_post_summary":"

Summary: Learn how to use Windows PowerShell and Active Directory cmdlets to document your Active Directory configuration.   Hey, Scripting Guy! I recently inherited an Active Directory. By this, I mean the network administrator quit. He did not give any notice, and it appears he took any documentation he may have created with him. He […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/12511","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/595"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=12511"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/12511\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=12511"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=12511"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=12511"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}