Jeramy Thompson

Remote Server Administration Tools for Windows 8 enables IT administrators to manage roles and features that are installed on computers that are running Windows Server 2012 from a remote computer that is running Windows 8. http://www.microsoft.com/en-us/download/details.aspx?id=28972 Overview Remote Server Administration Tools for Windows 8 includes Server Manager, Microsoft Management Console (MMC) snap-ins, consoles, Windows PowerShell cmdlets and providers, and command-line tools for managing roles and features that run on Windows Server 2012. In limited cases, the tools can be used to manage roles and features that are running on Windows Server 2008 R2 or Windows Server 2008. Some of the tools work for managing roles and features on Windows Server 2003. Top of page System requirements Supported operating systems:  Windows 8, Windows 8 Pro **Remote Server Administration Tools for Windows 8 can be installed ONLY on computers that are running Windows 8.** Remote Serv

http://www.windows-server-launch.com/Home

Microsoft has released a free E-Book for Server 2012. http://blogs.msdn.com/b/microsoft_press/archive/2012/09/05/free-ebook-introducing-windows-server-2012-rtm-edition.aspx?Loc=zTS3z&type=zDLz&media=zBKz&prog=zPressz&prod=zWSz

Checking hard drive space gets old, and if you want historical data it was a manual processes, so i created this script i run once a day to update a SQL database, and connect to it from excel to give me a historical data usage on our shared drives. Enjoy.

So the other day it was brought up to give a user access to see what users are in a specific set of groups in a specific OU. I did not want to install the admin tools just so they could use the ActiveDirectory modules, so i had to write this script using only ADSI. using ADSI only requires the end user to have read access to the objects. Here ya go have fun. # Group enumerator script by Jeramy Thompson # Downloaded from http://jeramythompson.blogspot.com/ # Change $ouPath to the path of groups you want to enumerate # To popluate different user properties # change $userCN.mail to $userCN.(property) for example # if you wanted the samaccount name change it to # $userCN.sAMAccountName # # # $ouPath = "OU=OUNAME,DC=netbiosdomain,DC=domain,DC=com" [void][System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms") [void][System.Reflection.Assembly]::LoadWithPartialName("System.Drawing") $Form1 = New-Object System.Windows.F

So I was all gung-ho about getting my servers upgraded to 2012. I had done all my testing on the RC's , had my documentation all setup and ready to go then ran into these issues: Windows 2012 VM Freezes or reboots host 2008 R2 SP1 - I actually read about this prior to installing it on my clusters. I was able to use the same hardware as a cluster node to verify that my shop is indeed having the issue. The best thing to do would be to upgrade the nodes to 2012 hyper-v 3.0. but again there are roadblocks in the way of that too! To backup the servers with DPM 2012 you need SystemCenter 2012 SP1 , as of right its still CTP2 so it is not going on my production servers. To manage the cluster nodes with VMM 2012, it needs, you guessed it, System Center 2012 SP1 . so as of right now I'm in a holding pattern for my production servers until SP1 is released. Update for HP customers:

So this was just a flat out weird issue that i was not able to lock down the cause of the issue but did find a fix. After reading countless articles on TechNet, asking questions   , and even creating a support ticket with Microsoft (I didnt even get to utilize them), I found the fix. Im Assuming that KB2706783 caused the issue. While waiting for microsoft to start the incident process, I was getting ready to send some tapes offsite, and noticed not only did the console crash but reports were not able to be generated any more either. on the server navigate here http://localhost/Reports_MSDPM2012/Pages/Folder.aspx click the DPMReports_* click DPMReporterDataSource Now here is where the issue was,the credintails were set to "DPMR$COMPUTERNAME" i have no idea where this came from or the password, i changed this part to "Windows Integrated Security" Now Reports work again, and so does the console. -Update- This is not a complete fix, just a step