SCOM Me this, PowerShell Me that! (Dynamics AX 2012)
So, trying to have an inventive title, the "SCOM Me this, PowerShell Me that! (Dynamics AX 2012)" is in reference to some of the key technologies that are being used from the rest of the Microsoft Stack, to help make lives easier, in terms of Manageability and Microsoft Dynamics AX 2012.
One of the first area's of improvements is around the SCOM Pack for Microsoft Dynamics AX 2012. This is, System Center Operation Manager Pack. This exists with Microsoft Dynamics AX 2009, but in a *very* limited basis.
So much so, that not a lot of people actually are moved to make use of the SCOM Pack for Microsoft Dynamics AX 2009. Well welcome to Dynamics AX 2012!
The amount of detail and effort that has went into the SCOM Pack for Microsoft Dynamics AX 2012 is amazing!
This means, that for anyone that has more than instance, and more than a single AOS, with anything beyond the core area of AX, needs to invest in SCOM and make use of this great tool.
Something I also mentioned above, is PowerShell. How much have we been talking about PowerShell? I believe in PowerShell!
With Microsoft Dynamics AX 2012, so much around Manageability improvements exists around the use of PowerShell, and delivered Microsoft Developed, PS CmdLet assemblies!
I went to the Reports Deployment session, and the entire session was focused around PowerShell, and a set of PowerShell scripts and Cmdlets that are used by said scripts to deploy and manage the deployment of Report Elements and Artifacts.
PowerShell is also a key piece to the SCOM management pack, as well as other area's like automating the deployment of .axmodel files from one instance to another.
What using the ISE (Integrated Scripting Editor) of PowerShell, and PowerShell framework itself brings to Microsoft Dynamics AX 2012 is greater flexibility, while promoting reuse, and lowering the manual administrative task associated with the many different aspects that exists for a Microsoft Dynamics AX 2012 deployment.
With these two key area's, it's important for a Dynamics AX Architect, Technical Engineer and Admin to learn now the syntax, usage, and ins and outs of. To see how this can help save time, promote reuse, and help lower the TCO of having Microsoft Dynamics AX 2012 as the ERP of choice for a company.
As more and more session content become ready in the CTP release coming soon, a lot of references, example PowerShell scripts, and usage highlights will be seen right here just on these topics! (Among others!)
That's all for now, and I hope you enjoy the second installment of Post #DAXCONF 11 coverage. This should be used as a build up to Convergence 2011, being held in Atlanta again this year! I am planning to be there myself.
Check back soon, as more to come!
"Visit the Dynamics AX Community Page today!"
One of the first area's of improvements is around the SCOM Pack for Microsoft Dynamics AX 2012. This is, System Center Operation Manager Pack. This exists with Microsoft Dynamics AX 2009, but in a *very* limited basis.
So much so, that not a lot of people actually are moved to make use of the SCOM Pack for Microsoft Dynamics AX 2009. Well welcome to Dynamics AX 2012!
The amount of detail and effort that has went into the SCOM Pack for Microsoft Dynamics AX 2012 is amazing!
- Diagram view of an instance, and all parts that make said instance up
- Ability to remotely restart services. (Thanks PowerShell!)
- Drain users, check online users, all from SCOM console
- Most all Admin task, from within the SCOM console. Less having to be done directly through Dynamics AX itself
- Total visibility through the entire enterprise, and the many instances, like Dev, Test and Prod - for a company
- Much more!
This means, that for anyone that has more than instance, and more than a single AOS, with anything beyond the core area of AX, needs to invest in SCOM and make use of this great tool.
Something I also mentioned above, is PowerShell. How much have we been talking about PowerShell? I believe in PowerShell!
With Microsoft Dynamics AX 2012, so much around Manageability improvements exists around the use of PowerShell, and delivered Microsoft Developed, PS CmdLet assemblies!
I went to the Reports Deployment session, and the entire session was focused around PowerShell, and a set of PowerShell scripts and Cmdlets that are used by said scripts to deploy and manage the deployment of Report Elements and Artifacts.
PowerShell is also a key piece to the SCOM management pack, as well as other area's like automating the deployment of .axmodel files from one instance to another.
What using the ISE (Integrated Scripting Editor) of PowerShell, and PowerShell framework itself brings to Microsoft Dynamics AX 2012 is greater flexibility, while promoting reuse, and lowering the manual administrative task associated with the many different aspects that exists for a Microsoft Dynamics AX 2012 deployment.
With these two key area's, it's important for a Dynamics AX Architect, Technical Engineer and Admin to learn now the syntax, usage, and ins and outs of. To see how this can help save time, promote reuse, and help lower the TCO of having Microsoft Dynamics AX 2012 as the ERP of choice for a company.
As more and more session content become ready in the CTP release coming soon, a lot of references, example PowerShell scripts, and usage highlights will be seen right here just on these topics! (Among others!)
That's all for now, and I hope you enjoy the second installment of Post #DAXCONF 11 coverage. This should be used as a build up to Convergence 2011, being held in Atlanta again this year! I am planning to be there myself.
Check back soon, as more to come!
Labels: DAXCONF, Dynamics AX, Dynamics AX 2012, Dynamics AX 6.0, ISE, Microsoft, PowerShell, PS, SCOM, SCOM Management Pack
posted by brandon | 2:43 PM
2 Comments:
Powershell remoting allows to do almost everything over network, even on several computers in the same time (simply specify a list of computers and go!). I used it with AX2009 and I'm quite happy with it. BTW take a look at PowerGUI.
With cmdlets for manipulations with models, I expect that automated AX deployments will be much easier than ever before.
Any idea if the AX2012 Management Pack also monitors the older AX 2009 servers? Can we replace the AX2009 MP with it?
Post a Comment
<< Home