Skip to main content

Dealing with Property Names that Start with #

By
Tonight I’m doing my class maintenance on Microsoft Official Course 20697-2B Deploying and Managing Windows 10 Using Enterprise Services. For those of you who have taken my classes, you know I provide a OneDrive full of goodies to each class.  Right now I’m playing around with Chapter 3 and the migration of user data.  While working with size estimates for the migration store, I decided to import the XML file the ScanState.exe /p produces.

PS USMT:> $StorageInfo.Premigration.storeSize.Size | Get-Member –MemberType Properties

   TypeName: System.Xml.XmlElement

Name        MemberType Definition
----        ---------- ----------
#text       Property   string #text {get;set;}
clusterSize Property   string clusterSize {get;set;}

So, do you see the problem?  Take a look at the property called #text.  In PowerShell, the # symbol is the start of an inline comment.  That means that anything typed after it will not be processed.  That kind of makes calling this property a bit of a problem.  We can fix it.

If you do not code this correctly, PowerShell will interpret the # and everything after it as a comment.  The green font in the code demonstrates this.

$StorageInfo.PreMigration.StoreSize.Size |
    Select-Object -Property CluserSize,
        @{
           N = "SizeMB"
           E = {($_.#Text / 1MB).ToString('#.##') -as [Single]}
        }

To fix this problem, encapsulate our problematic property name inside of double quotes.

$StorageInfo.PreMigration.StoreSize.Size |
    Select-Object -Property CluserSize,
        @{
           N = "SizeMB"
           E = {($_."#Text" / 1MB).ToString('#.##') -as [Single]}
        }

Now you will be able to call the property and use it.



Labels:

Comments

Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Error icon when creating a GPO Preference drive map

By
You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the ma...
1 comment
Read more