Jonathan, et al.
So the root cause of my issue turned out to be a full hard drive. During our last patch cycle a DotNet 4 update wrote a slew of .txt and .cab file to the %systemroot%/temp folder which basically filled up the system partition. This was preventing the PoSh script writing output so the script was not able to complete. Who would have THUNK!. I immediately checked my other polling engine servers and while that had many of the same .txt & .cab file they did not has as many as the problem machine. So in a not shell it was not an issue, per say, with Solarwinds SAM but was actually a system resources issue.
I'm planning on loading the template to the content exchange. It's great since it goes out and checks the replication between domain controllers. Only caveat is you must have Server 2008 or later since you will need to be running AD web service.
I have another application monitor that actually reports the time is takes for a change to replicate to all Domain Controllers. We have a large AD environment with DCs all across the country. So knowing that it only takes 72.23 seconds for a change to occur on all DCs is a plus debunking AD as the root cause for an issue. Both are PoSh based and do not need to run with elevated privileges a powerless service account is all you need!
Thanks