- #WINDOWS 10 GET CUSTOM PROPERTY OUT OF FILE DETAILS WINDOWS 10#
- #WINDOWS 10 GET CUSTOM PROPERTY OUT OF FILE DETAILS CODE#
Of course, if you want those amazing-looking customized desktops, you’ll have to spend a bit more time. As I mentioned, this only took me about 30 minutes to do and it makes your desktop look unique.
#WINDOWS 10 GET CUSTOM PROPERTY OUT OF FILE DETAILS WINDOWS 10#
After playing around with the programs I’m going to mention below, I managed to get my desktop to look like this, which is not great, but OK for spending only about half an hour.Īs you can see, I have a custom sidebar on the right with links to my favorite Windows locations, some custom links with icons on the left hand side instead of my normal desktop icons, a custom Windows 10 Start Menu, some weather info at the bottom right, a cool looking circle that tells the current time and a small search box for quickly using Google. Once the AD services are restarted successfully, repeat the same command that we ran at the start of this section.Very standard and nothing exciting going on here.Get-Service NTDS -DependentServices | Restart-Service -Force -Verbose To restart the services using PowerShell, run the following command: Now that the custom attributes are created, you need to restart the Active Directory Domain Services for the changes to take effect.It could take a while, depending on the size of your Active Directory infrastructure. After creating the attributes in the AD schema, wait a bit so that the changes can replicate to other domain controllers in your forest.To create the second attribute (Campus ID), change the values of the attributeName, attributeDesc, and OID variables in the script and execute it again.If you do not get any errors, your custom attribute (Campus Name) has been added.After making the changes shown above, you can click the "Run Script" button or press the "F5" key to execute the script.See the inline comments for more help on the supported attribute values. You can also change the values of oMSyntax, attributeSyntax, and indexable variables.The value of the OID variable will be generated by the Generate-OID.ps1 script that we created in the previous section.At a minimum, you need to change the values of the attributeName, attributeDesc, and OID variables, which are marked in red in the image above.There are certain sections that you need to change according to your requirements before you can execute this code.
#WINDOWS 10 GET CUSTOM PROPERTY OUT OF FILE DETAILS CODE#
Please don't execute this code straightaway. Each line of this code has a comment to help explain what that line is doing.The script is also attached for reference. $GUIDPart += ::Parse($GUID.SubString(30,6), "AllowHexSpecifier") $GUIDPart += ::Parse($GUID.SubString(24,6), "AllowHexSpecifier") $GUIDPart += ::Parse($GUID.SubString(19,4), "AllowHexSpecifier") $GUIDPart += ::Parse($GUID.SubString(14,4), "AllowHexSpecifier") $GUIDPart += ::Parse($GUID.SubString(9,4), "AllowHexSpecifier") $GUIDPart += ::Parse($GUID.SubString(4,4), "AllowHexSpecifier") $GUIDPart = += ::Parse($GUID.SubString(0,4), "AllowHexSpecifier") We will create a script and name it " Generate-OID.ps1."Ĭopy the following code and save it in a file named " Generate-OID.ps1." $Prefix = "1.2.840.1135.2554" First, we'll create a script to generate the OIDs for the custom attributes (Campus Name and Campus ID) that we will be adding to our AD schema. You can perform these steps directly on a DC or via an interactive PowerShell session (Enter-PSSession) to a DC.Īll AD objects have a unique identifier called the Object Identifier (OID).The Active Directory module for Windows PowerShell must be installed on the DC.You must be a member of the Active Directory Schema Admins group.To perform the steps mentioned in this article, you must meet the following requirements:
0 kommentar(er)
