Basic Debugging in SAPIEN PowerShell Studio 2015

I wanted to share a little debugging trick with SAPIEN PowerShell Studio 2015. Logic bugs are not a fun. Essentially, your script is doing exactly what you told it to do, but it is not what you wanted it to do. Most likely, the contents of memory are not what you expected. SAPIEN PowerShell Studio 2015 has both a Variable and a Watch window to help you in your debugging efforts. Take a look at this code:

There is nothing wrong with it. I just want to use very basic code. By pressing Ctrl – F5 you will run this code normally. Pressing F5 runs the code in Debug Mode. In Debug Mode, nothing special happens. You have to set a break point.

Above, I clicked on line 16 and pressed F9. This is where execution of the code will stop and allow you to examine the contents of memory. Press F5 to see what happens next.

You can see the arrow beside line 16. This is where we currently are suspending execution. The Variables window is opened and I scrolled to the bottom of the list to see our variables. Variable Z is not in memory since we stopped execution on its line. While scrolling through this list, you may notice that all data in memory is being displayed. If you want to focus on a specific variable and ignore the rest, use the watch window. Right click X and select Add to Watch. Now click on the Watch tab.

Each time you run this code, this variable will be in the watch window until you remove it.

By pressing F5 again, you will resume script execution.

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