Jeramy Thompson

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

Though id make a quick post about the latest DPM blunder and easy fix. Once you upgrade to update roll up 2 KB2706783  , you will need to upgrade all the agents on your servers. The on domain servers you can click on the console and upgrade them quickly, however for your off domain (untrusted) servers you have to manually install the update. Now reading this would tell you that the folder is located in the C:\Program Files\Microsoft System Center 2012\DPM\DPM\ProtectionAgents\RA\ folder. well that's not true. I guess the programmers at Microsoft fell asleep at the wheel and put it in the "C:\Program Files\Microsoft System Center 2012\DPM\DPM\agents\RA" folder. not sure why its there but it is, just copy that folder to your servers and run the installer, it will update and you will be good to go.

With the RTM in early August, MS has released Windows 8 in its various flavors to TechNet and MSDN. Current Releases Windows 8 (x86) - DVD (English) Windows 8 (x86) - DVD (English-United Kingdom) Windows 8 (x64) - DVD (English) Windows 8 (x86) - DVD (English-United Kingdom) Windows 8 Enterprise (x86) - DVD (English) Windows 8 Enterprise (x86) - DVD (English-United Kingdom) Windows 8 Enterprise (x64) - DVD (English) Windows 8 Enterprise (x64) - DVD (English-United Kingdom) Windows 8 Enterprise N (x64) - DVD (English) Windows 8 Enterprise N (x64) - DVD (English-United Kingdom) Windows 8 Enterprise N (x86) - DVD (English) Windows 8 Enterprise N (x86) - DVD (English-United Kingdom) Windows 8 N (x86) - DVD (English) Windows 8 N (x86) - DVD (English-United Kingdom) Windows 8 N (x64) - DVD (English) Windows 8 N (x64) - DVD (English-United Kingdom) Windows 8 Pro VL (x86) - DVD (English) Windows 8 Pro VL (x86) - DVD (English-United Kingdom) Windows 8 Pro VL (x64) - DVD (Engl

I noticed that after installing windows updates for 8/14 KB2647753 , installed successfully, then requested that it be installed again. It does show up when you run in systeminfo. Waiting on a response from Microsoft on this issue here http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/6e8d5ffd-045f-4184-98a0-b79109361ded created this quick powershell script to show the version number to verify against the website. Get-Item $env:windir\system32\localspl.dll | foreach-object {$L = $_.VersionInfo.FileVersion} Get-Item $env:windir\system32\win32spl.dll | foreach-object {$W =  $_.VersionInfo.FileVersion} Get-Item $env:windir\system32\spoolsv.exe | foreach-object {$S = $_.VersionInfo.FileVersion} $L = $L.substring(0, $L.IndexOf("",15)) $W = $W.substring(0, $W.IndexOf("",15)) $S = $S.substring(0, $S.IndexOf("",15)) Write-host "localspl.dll -FileVersion- $L win32spl.dll -FileVersion- $W spoolsv.exe -FileVersion-

I wrote a powershell script to fix this issue in 2010, it does not appear to be an issue in 2012. a full explanation i got from here.  Enjoy $ServerInstance = "DPMSERVER\MSDPM2012" $Database = "DPMDB" $ConnectionTimeout = 30 $Query = "select media.BarcodeValue, media.SlotNum, media.MediaId, gmedia.MediaPoolId from tbl_MM_Global_ArchiveMedia gmedia  inner join tbl_MM_Media media on gmedia.MediaId = media.GlobalMediaId " $QueryTimeout = 120 $conn=new-object System.Data.SqlClient.SQLConnection $ConnectionString = "Server={0};Database={1};Integrated Security=True;Connect Timeout={2}" -f $ServerInstance,$Database,$ConnectionTimeout $conn.ConnectionString=$ConnectionString $conn.Open() $cmd=new-object system.Data.SqlClient.SqlCommand($Query,$conn) $cmd.CommandTimeout=$QueryTimeout $ds=New-Object system.Data.DataSet $da=New-Object system.Data.SqlClient.SqlDataAdapter($cmd) [void]$da.fill($ds)  $conn.Close()

If you an administrator you are aware of  KB2718704  and its exploits via the Flame software. After patching my DPM server it appears all non domain servers are no longer allowing the DPM 2012 server to connect. to fix the error re-attach the servers in DPM Management Shell attach-nondomainserver dpmservername   -psname remoteservername   -username remotelocalusername

So i thought id put in some notes on configuring a Hyper-V Cluster on 2008 R2 SP1 core. in my scenario i an using 4 nics team for Hyper-V data, 1 nic for management , one for cluster traffic and one for live migration data. I am also using 8GB FC clusters consists of 5 nodes (removing the need for a quorum drive) This is only connected to 1 VLAN , if you need mutiple VLANS, create them before creating your cluster as it will be easier. one tool you will need in this setup is nvspbind.exe , this allows for the configuration of network services tied to the adapters. first you will want to install all your cluster servers exactly the same with the same hardware etc. Then install the OS (im using 2008 R2 Datacenter) and select the Core installation once installed loginto the server , you will get a command prompt install the SNMP feature Dism /online /enable-feature /featurename:SNMP-S Enable Remote Administration of Firewall (optional) netsh advfirewall set currentprofil

So upgrading is very simple, there are many different post on how to upgrade , and its mostly point and click, however there are some things you should do to "make it work", or maybe it was just me. also depending on how large your infrastructure is, now backups can run until the whole process is done, that means you need your dpm server on 2012, and client agents on on 2012 (2003 servers may require a reboot) 1st backup your 2010 database run your upgrade once completed reboot then BACK UP your 2012 DATABASE NOW! this will save you frustration later down the road, just put it on disk somewhere. FYI, if your using the SQL that came with DPM, it does not include SP1 (yeah that's right), update this later. everything will be out of sync begin sync them now. if you remember setting the tape write period ratio along time ago, guess what, it dosen't exist any more in powershell Set-DPMGlobalProperty –DPMServerName -TapeWritePeriodRatio you now get to set