At this moment I've taken everything I own and moved it 1530km south from Santa down to a small town called Getinge.
Here I've entered a domestic relationship with a beautiful girl so this means that I'm not currently in sync with anything!
onsdag 28 maj 2014
torsdag 22 maj 2014
Implementing a new DPM solution in Santas new workshop, and instantly ending up in problems!
Here I am wrapping scripts in all joy when I stumble upon a few DPM errors in a new envirorment, and instantly I thought "Wait? What, an error already? But I haven't done anything yet!"
Here is the error(s) I received:
DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 521, WSB Error Code: 0x17663A0). (ID 30229 Details: Internal error code: 0x80990ED0)
DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 546, WSB Error Code: 0xD317E0). (ID 30229 Details: Internal error code: 0x80990ED0)
From those error messages I can understand DPM, Cannot, .. you get the point.
After some reasearching it seems that this is cuases by the recovery volume being too small. You know that recovery volume that's supposed to be 350MB in Windows Server 2012 R2? It seems that it's only 300MB and that is too small for DPM and a BareMetal Restore backup option.
So, dig out your command prompt and assign a new location for the shadowstorage for the recovery volume by first listing where you have the recovery volume with vssadmin list volumes that will give you a something like this:
Volume path: C:\
Here is the error(s) I received:
DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 521, WSB Error Code: 0x17663A0). (ID 30229 Details: Internal error code: 0x80990ED0)
DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 546, WSB Error Code: 0xD317E0). (ID 30229 Details: Internal error code: 0x80990ED0)
From those error messages I can understand DPM, Cannot, .. you get the point.
After some reasearching it seems that this is cuases by the recovery volume being too small. You know that recovery volume that's supposed to be 350MB in Windows Server 2012 R2? It seems that it's only 300MB and that is too small for DPM and a BareMetal Restore backup option.
So, dig out your command prompt and assign a new location for the shadowstorage for the recovery volume by first listing where you have the recovery volume with vssadmin list volumes that will give you a something like this:
Volume path: C:\
Volume name: \\?\Volume{7815fed2-f917-44b3-b3af-f9bb2bdb86fa}\
Volume path: N:\
Volume name: \\?\Volume{9e3e1356-d856-11e3-80b7-00155d016606}\
Volume path: F:\
Volume name: \\?\Volume{9e3e135a-d856-11e3-80b7-00155d016606}\
Volume path: \\?\Volume{d02c7a79-db9b-4a55-99df-f697a3dc2b6c}\
Volume name: \\?\Volume{d02c7a79-db9b-4a55-99df-f697a3dc2b6c}\
After that, either shrink an existing volume or add some more space, where doesnt matter as long as you can spare it.
Then execute the command vssadmin add shadowstorage /for:<the volume path for the only volume with no drive letter, i.e \\?\Volume{d02c7a79-db9b-4a55-99df-f697a3dc2b6c}\> /on=S: /maxsize=900MB (You can pick from a range from bytes to Exabytes or UNBOUNDED)
If you get an error message saying Error: The specified shadow copy storage association already exists. Then you have to delete the existing association before readding a new one.
Hope this helped anyone! Besides me that is!
Have a great day out there!
/Joseph
onsdag 14 maj 2014
Inventory done with Powershell
I was sitting in my corner of the workshop minding my own business when I got the question "Hey Joseph, can you find out where the XXX account is used in the domain?"
Without hessitation I answer "Of course I can! And it wont take long!"
I was all joy and happiness beacuse I knew that I could do all the inventory from Powershell but I had no clue on how to do it programmatically but after a quick search on the internet I found what I needed.
Since Santas Workshop has a few SQL servers I wanted to search through them as well just to make sure that the account was not used within SQL and I stumble across a superb too called SQL PowerDoc and it's written by Kendal VanDyke.
That took care of the SQL Servers, but how about all services and if there are any Task Sequences using this XXX account?
Then I found this great script called Get-RunAsAccount.ps1 from Jan Egil Ring's blog that pointed me in the right direction. This little nifty script finds pretty much all that I was interested in.
In all it took me just a few (2-3) hours to do an inventory of all the servers out there in the Santas Workshop and it's all done with Powershell.
I have a colleauge that's not that much into Powershell (He's stuck in the VB world) and he was in awe over how easy it is to work with powershell.
Ok, so I'll head back to the cellar and continue to build the cloud solution for Santa so he finally can get migrated from the competitors onto Hyper-V
/Joseph
Without hessitation I answer "Of course I can! And it wont take long!"
I was all joy and happiness beacuse I knew that I could do all the inventory from Powershell but I had no clue on how to do it programmatically but after a quick search on the internet I found what I needed.
Since Santas Workshop has a few SQL servers I wanted to search through them as well just to make sure that the account was not used within SQL and I stumble across a superb too called SQL PowerDoc and it's written by Kendal VanDyke.
That took care of the SQL Servers, but how about all services and if there are any Task Sequences using this XXX account?
Then I found this great script called Get-RunAsAccount.ps1 from Jan Egil Ring's blog that pointed me in the right direction. This little nifty script finds pretty much all that I was interested in.
In all it took me just a few (2-3) hours to do an inventory of all the servers out there in the Santas Workshop and it's all done with Powershell.
I have a colleauge that's not that much into Powershell (He's stuck in the VB world) and he was in awe over how easy it is to work with powershell.
Ok, so I'll head back to the cellar and continue to build the cloud solution for Santa so he finally can get migrated from the competitors onto Hyper-V
/Joseph
tisdag 13 maj 2014
TechEd and Powershell
I was working and watching the live stream over at channel9.msdn.com when Jeffry Snover and Don Jones was presenting Powershell and how they use it. What struck me was that they used it in (almost) the same way that I do! Searching commands using Get-Command, Show-Object and so on. And something that struck me was how much they were using get-help, and that is somewhat of a ego-boost for a rookie powershell'er as myself!
One of the news that was presented yesterday was Powershell.Get - a way of easily searching and installing modules from a invite-only repoistory. This is something that I look forward to. They mentioned as well about the new package called oneget where you easily can add program such as Putty by just type Install-Package putty and powershell runs out on the internet and downloads and installs the package for you.
The fature, oneget, requires Windows Management Framework 5.0 which still is in Preview version.
Well, I'll better focus on building a cloud for Santa and his workshop before I escape from the artic regions!
One of the news that was presented yesterday was Powershell.Get - a way of easily searching and installing modules from a invite-only repoistory. This is something that I look forward to. They mentioned as well about the new package called oneget where you easily can add program such as Putty by just type Install-Package putty and powershell runs out on the internet and downloads and installs the package for you.
The fature, oneget, requires Windows Management Framework 5.0 which still is in Preview version.
Well, I'll better focus on building a cloud for Santa and his workshop before I escape from the artic regions!
måndag 12 maj 2014
Watch MSTechED live
Oh, I failed to mention that you can watch Tech ED live over at channel9.msdn.com/ so head over there and enjoy the new announcements from Microsoft!
Lack of updates
I have been terrible when it comes to updating this blog, and the reason for this is that I am moving 1500km South in Sweden (Halland), with that fact in hand I have had a tonne of work to finish before the move.
One part of that is System Center Virtual Machine Manager. Santa and his Workshop is currently in the workings of deploying SCVMM to replace their current Virtual solution.
I will do my best to update this blog!
Over and out
Joseph
One part of that is System Center Virtual Machine Manager. Santa and his Workshop is currently in the workings of deploying SCVMM to replace their current Virtual solution.
I will do my best to update this blog!
Over and out
Joseph
Prenumerera på:
Inlägg (Atom)