Infront released a new management pack, a while ago, for FREE, to the community via System Center Central.
http://www.systemcentercentral.com/tabid/143/indexid/94055/default.aspx?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+systemcentercentral%2Fblogs+%28Blogs+at+System+Center+Central%29
This management pack will give you a deeper insight into your virtual machines including recognising which platform (Hyper-V, VMware & Citrix), which hosts they're located on, if VM Tools are installed and the version.
(footnote. I actually wrote this post the day they released it, but forgot to post it /facepalm)
Thursday, 15 November 2012
Wednesday, 14 November 2012
AWOL
Posts have been very light on the ground of recent I'm afraid due to just how busy I've been both at work and personally.
I'm on the road and in hotels for the next week or so and hopefully that will give me the some time to catch back up.
Some of the posts I'm hoping to get done soon will be around:
I'm on the road and in hotels for the next week or so and hopefully that will give me the some time to catch back up.
Some of the posts I'm hoping to get done soon will be around:
- SCOM noise and advice
- System Center installation PowerShell scripts
- Orchestrator Runbooks
- Windows 8 deployment customisation
- SCSM customisation and extension
- System Center console deployments via ConfigMgr
- Other random bits...
Thursday, 25 October 2012
Windows 8 Skype App to the Rescue!
Sweet... That about sums up my thoughts for the new Skype App.
Not that I've used it in anger or that I'm a long time Skype user, no.
In fact, before today, I've never used Skype. Of course I had heard of it and was aware what it did, just that I've never had a need for it.
Until today. Just hours after it being released I found myself on a conference call where the only available audio option was via dialling the states.
Say what?!?!? Hang on, I'm on a mobile here in the UK, this is going to get expensive really quickly.
So knowing that Skype had just hit the store I quickly installed it (I love one click installs!) it used my Microsoft ID to single sign on (SSO) straight in, allowed me to dial a US Toll Free number as if I was in the states and then docked nicely to the side while I watched the presentation.
Not that I've used it in anger or that I'm a long time Skype user, no.
In fact, before today, I've never used Skype. Of course I had heard of it and was aware what it did, just that I've never had a need for it.
Until today. Just hours after it being released I found myself on a conference call where the only available audio option was via dialling the states.
Say what?!?!? Hang on, I'm on a mobile here in the UK, this is going to get expensive really quickly.
So knowing that Skype had just hit the store I quickly installed it (I love one click installs!) it used my Microsoft ID to single sign on (SSO) straight in, allowed me to dial a US Toll Free number as if I was in the states and then docked nicely to the side while I watched the presentation.
Skype App to the rescue!! Now I'm hoping that it works nicely on my Surface RT (fingers crossed it does come tomorrow and not 2nd Nov...)
Friday, 19 October 2012
System Center 2012 - Service Manager Cookbook
Well, it's a wrap!!
The System Center 2012 Service Manager Cookbook went into the production phase today and should be available shortly to purchase in it's final version opposed to the RaW version that was available previously.
I really do hope that people find this a useful resource when working with Service Manager and it's been a pleasure working with the top guys from Europe as a team on this project, those guys seriously think on a whole new level around Service Manager and in fact System Center in general!
For now, enjoy the eye candy that is the final cover of the book with a spectacular view from the top of Europe.
The System Center 2012 Service Manager Cookbook went into the production phase today and should be available shortly to purchase in it's final version opposed to the RaW version that was available previously.
I really do hope that people find this a useful resource when working with Service Manager and it's been a pleasure working with the top guys from Europe as a team on this project, those guys seriously think on a whole new level around Service Manager and in fact System Center in general!
For now, enjoy the eye candy that is the final cover of the book with a spectacular view from the top of Europe.
System Center 2012 - EndPoint Protection Cookbook
While I'm waiting for the PackT publishers to spit and polish the Service Manager Cookbook I thought I would download another of their offerings.
So after digging through their library I settled on the System Center 2012 EndPoint Protection Cookbook by Andrew Plue.
Once I've read it or most of it I'll pop a little review online.
So after digging through their library I settled on the System Center 2012 EndPoint Protection Cookbook by Andrew Plue.
Once I've read it or most of it I'll pop a little review online.
The book can be found for purchase here: http://www.packtpub.com/microsoft-system-center-2012-endpoint-protection-cookbook/book
Friday, 12 October 2012
VMM 2012 SP1 (Beta) with Server 2012 Hyper-V Issue
After migrating my 2008 R2 cluster across to Server 2012 I was having problems adding in the cluster/hosts to SC2012 Virtual Machine Manager SP1.
The cluster could be discovered and imported fine, but a few minutes later would report back that it could no longer be managed.
It turns out that because on the rebuild I didn't make the hosts DC's (it's a testlab before someone comments on best practise!!) so the computer accounts got placed into an OU along with the normal servers that had a Group Policy applying some WinRM settings.
Unfortunately doing a winrm /qc or allowing VMM to check that WinRM is enabled doesn't set/check all the required settings are actually in place.
Having a look around I found the following TechNet forum post from Wes Kroesbergen who listed a registry key that's advisable to have set, plus the winrm commands to set all of the required settings.
http://social.technet.microsoft.com/Forums/en-US/virtualmachingmgrhyperv/thread/4bd9be4b-0ff9-46f3-bf32-1b7c1245c494
Wrap the below into a batch file (you can't use these commands via PowerShell before you try), run it on your Hyper-V hosts and you're good to go!
reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f
winrm set winrm/config/service/auth @{CredSSP='True'}
winrm set winrm/config/winrs @{AllowRemoteShellAccess='True'}
winrm set winrm/config/winrs @{MaxMemoryPerShellMB='2048'}
winrm set winrm/config/client @{TrustedHosts='*'}
winrm set winrm/config/client/auth @{CredSSP='True'}
The cluster could be discovered and imported fine, but a few minutes later would report back that it could no longer be managed.
It turns out that because on the rebuild I didn't make the hosts DC's (it's a testlab before someone comments on best practise!!) so the computer accounts got placed into an OU along with the normal servers that had a Group Policy applying some WinRM settings.
Unfortunately doing a winrm /qc or allowing VMM to check that WinRM is enabled doesn't set/check all the required settings are actually in place.
Having a look around I found the following TechNet forum post from Wes Kroesbergen who listed a registry key that's advisable to have set, plus the winrm commands to set all of the required settings.
http://social.technet.microsoft.com/Forums/en-US/virtualmachingmgrhyperv/thread/4bd9be4b-0ff9-46f3-bf32-1b7c1245c494
Wrap the below into a batch file (you can't use these commands via PowerShell before you try), run it on your Hyper-V hosts and you're good to go!
reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f
winrm set winrm/config/service/auth @{CredSSP='True'}
winrm set winrm/config/winrs @{AllowRemoteShellAccess='True'}
winrm set winrm/config/winrs @{MaxMemoryPerShellMB='2048'}
winrm set winrm/config/client @{TrustedHosts='*'}
winrm set winrm/config/client/auth @{CredSSP='True'}
SCVMM 2012 SP1 - Missing properties and unable to refresh VM
Giddy as a kid in a sweet shop I migrated my testlab cluster to Server 2012, migrated my VM's across and installed System Center 2012 Virtual Machine Manager SP1 to manage it.
Straight away I ran into some slightly strange issues.
Thankfully, last Friday (05/10/12) Mark at Microsoft posted the following suggestion to try:
On the Hyper-V hosts run the following PowerShell commands
Import-Module Hyper-V
Get-WmiObject –Namespace “root\virtualization\v2” Msvm_PlannedComputerSystem | foreach{Get-VM –Id $_.Name} | Remove-VM –Force
Once this has been run on your hosts, refreshing the VM's should work successfully and all of the missing/default hardware config should be updated and displayed.
It looks like this is to do with the hosts having the VM stuck in a temporary state, even if brought across as a planned import or migration.
The problem is now at least known about and should be fixed/handled in the next release of the Service Pack.
Straight away I ran into some slightly strange issues.
- Majority of the Auto Discovered VM's refused to see hardware configuration properties such as:
Virtual Hard Disks and Controllers
Virtual Network Cards - Majority of the Auto Discovered VM's left hardware configuration properties at defaults, such as:
Processor Count and Memory Amount
High Availability Status - Every time I tried to refresh a VM I would get the error:
Error (2923)
A malformed response was received while trying to contact the VMM agent on hyperv01.domain.local.
Unspecified error (0x80004005)
Recommended Action
1) Ensure the VMM agent is installed and that the SCVMMAgent service is running.
2) If the SCVMMAgent service is running, restart the service, and then verify that WS-Management is installed correctly and that the WinRM service is running.
3) Check the manufacturers' Web sites to ensure that you have the latest drivers for your network adapters and other devices.
Thankfully, last Friday (05/10/12) Mark at Microsoft posted the following suggestion to try:
On the Hyper-V hosts run the following PowerShell commands
Import-Module Hyper-V
Get-WmiObject –Namespace “root\virtualization\v2” Msvm_PlannedComputerSystem | foreach{Get-VM –Id $_.Name} | Remove-VM –Force
Once this has been run on your hosts, refreshing the VM's should work successfully and all of the missing/default hardware config should be updated and displayed.
It looks like this is to do with the hosts having the VM stuck in a temporary state, even if brought across as a planned import or migration.
The problem is now at least known about and should be fixed/handled in the next release of the Service Pack.
Subscribe to:
Posts (Atom)