Odd Behavior When creating BAT Files with PowerShell

Just the fact the I’m using PowerShell to create BAT files is odd enough. This pesky little problem cost me many hours of precious time. Essentially, I’m writing some PowerShell code to look at some BAT files and then reconfigure them according to my scripts logic. That all works flawlessly. The problem is some extra bits added to the beginning of each line. I was using the Out-File cmdlet to save the new paths to the BAT file. Take a look at this one line:

"Dir" | Out-File –LiteralPath "J:\PSTest.bat"

Simple enough. It created a BAT file call PSTest with only one command, “DIR”. This is what happens when you run it.

What is the mysterious character in front of the “D”? I tried to implement this in several different ways. File redirection using “>>” did not work. It yielded the same results. I also tried the –encoding parameter of Out-File. Same result. Using Get-Content in PowerShell, Type in DOS, or even opening the file in Notepad would produce a normal looking file. No signs of the mysterious character. I finally settled on Add-Content.

Add-Content will add a line of text to a text file. Since this file would be changing often, I had to include code that would test for the existence of the file and remove it if it was already there:

# See is a configuration file already exists.

# Make sure it is empty.

If (Test-Path -Path "J:\PSTest.bat")

{

Remove-Item "J:\PSTest.bat"

}

Now I can add as many commands as I want by calling Add-Content.

Add-Content -Path "J:\PSTest.bat" -Value "DIR"

Now the mysterious character is no longer present and the batch file will execute normally.

Comments

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

Backup and Restore AD LDS with DSDBUTIL.exe

Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services. The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database. Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet. Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS. You may want to make sure the database is being backed up and also have a restore plan in place. Should the database become corrupt, the application that uses that database will fail. This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...

Jason Yoder, MCT

Search This Blog