We use System Cetner Orchestrator with the Orchestrator Integration Pack. In this Integration Pack there is an Activity “Start Runbook”. Which worked like a charm – till now.
We use this “Start Runbook” activity to start a runbook with parameters. We can use any string parameter in any length except XML strings. If the XML Input gets too long, the call fails. (see screenshot below).
This week I have been at the PowerShell Usergroup in Munich, Germany.
They wished to get information about PowerShell Profiles, so I commited a talk on PowerShell Profile. And here is the content.
There are 4 PowerShell Profiles loaded on startup of the console. But there can be some more Profiles in your environment. That is, beacause you have two PowerShell profiles per PowerShell console. So VSCode, PowerShell ISE and the PowerShell command prompt have two profiles each. One Profile is for All Users, one for the current user. Additionally you have got a PowerShell Profile for Windows PowerShell and a seperate one for PowerShell Core. So there can be some PowerShell Profiles on your computer.
Use the following command in your prefered console to get the actual profile pathes:
By the way, they are loaded in exactly this order (which makes sense).
What I have in my PSProfile
I talked about which PowerShell Profiles exists and also, what I have in my profile as an PowerShell automator. As an automator my focus is on execution duration, so the most relevant part is the execution time in the prompt. It looks like this in my console:
There are some more featues in my PSProfile prompt, eg the color of the provider is integrated in the path, for example FileSystem and registry:
We grant access to Service Manager Serrvice Requests using AD Groups in User Roles. When a User is added to the AD Group the permissions are not updated – so they do not see the additional Service Request in the portal.
There are two things to do:
Recycle App Pool
User has to re-login (not always)
Here is the code to Recyle the App pool for the standard HTML Portal and the ITNetX Portal:
Today I have been asked, what could be improved in the Azure Mobile App. Since I mainly use PowerShell, that is a bit of a challenge. In PowerShell there is no GUI – as you know. So I was thinking about ways to improve the Azure Mobile App.
I have multiple Azure AD and Live ID acounts – all can be managed in this app. And I see all subscriptions in each account. Very nice.
So my main purpose to look into the app are virtual machines. To look at the status and start or stop the machines.
So I figured out these three possibilities to improve the app:
Show all subscriptions in one list, not in Azure AD accounts
I would find it useful, to have all subscriptions in one list – not only all subscriptions for each AAD account. So I do not have to search for a Subscription in one of my accounts.
Favourites for all subscriptions
I would prefere, to have Favourites over all subscriptions – like the recent list in Office. In the recent list in Office there are all Documents of all Microsoft accounts together in one recent-list. So I do not have to change the account and the subscription, to get to the favourites. I simply have them.
This could be an additional feature. Favourites on subscription level AND Favourites for all subscriptions.
Make Favourites available in portal.azure.com
Make the Favourites available and editable in the web browser on the Azure portal.
So these are my current suggestions to the Azure Mobile App.