Hi
Meraki devices have status pages. These can be accessed by internal clients. See https://documentation.meraki.com/zGeneral_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page
Wireless Access points MR - http://ap.meraki.com Switches MS - http://switch.meraki.com Routers MX and Z1 - http://wired.meraki.com Any - http://setup.meraki.com This URL will work for any Cisco Meraki device, but will only access the first device in its path. For example, if you’re on a PC connected to a Meraki switch you can connect to http://switch.meraki.com/ which gives you a status page about your connection.
While hunting for some Hyper-V videos, I came across recorded sessions from the 4th Nordic Infrastructure Conference. No sales pitches, only some great talks from field hardened consultants. The sessions are focused on Enterprise Infrastructure (Microsoft Windows Server, System Centre, Azure, PowerShell DSC, Identity Management, Security/hacking).
Session Info http://2015.nicconf.com/sessions Recorded sessions: https://www.youtube.com/channel/UChu8zqu8d1mjWxNRLlGXUAw
We know Visual Studio Pro with MSDN gets you unlimited Windows Server (including Hyper-V for virtualisation) and unlimited SQL. This is a way of licensing Microsoft software in your on premises test and development environments.
You can now bring your own MSDN licences with you to Azure. This way the Microsoft software in your Windows and SQL VMs on Azure is already paid for and you pay the equivalent of Linux rates for Windows and SQL VMs on Azure.
Update: THIS WAS 2015 AND PRE COVID…
I’ve been reading about how distributed companies are operating. Companies with their servers running in the cloud don’t need a server room, or Office premises at all it seems. And there’s lots of them.
Wired article about Automatic, the company behind WordPress Lots of information at this clever URL WorkingRemote.ly Article about how Buffer do distributed working The Pros and Cons of Remote Work in Ops As a worker wouldn’t you like to skip the commuting?
Query for Bitlocker recovery keys (properties of machines) and then getting the owner of key. Using the useful (and free) Quest ActiveRoles commandlets but you can do this with regular activedirectory powershell module too. add-pssnapin quest.activeroles.admanagement -ErrorAction Silentlycontinue $DesktopsOU= "OU=Win7,OU=Workstations,DC=companyname,DC=com" # or whatever your machine OU is Get-QADObject -SizeLimit 0 -IncludedProperties Name,ParentContainer -SearchRoot $DesktopsOU | Where-Object {$_.type -eq "msFVE-RecoveryInformation"} | Foreach-Object {Split-Path -Path $_.ParentContainer -Leaf} | Select-Object -Unique The following page links to a script which will give you a CSV report http://blog.
When you get started with Amazon Web Services (AWS) one thing to do early is secure access to the web console. Rather than manage another set of user accounts you can reuse your corporate directory (Microsoft Active Directory) to login to the AWS console. You use AD Federation Services to do this. Also, if you keep your ADFS server internal, then your AWS console is not accessible from the public Internet.
At a conference yesterday there was the results of a survey into business and IT dept priorities and a discussion around how they differ: Business Priorities
1.Improving Efficiency
2.Deliver Operational Results
3.Improve Profitability
4.Reduce Enterprise Costs
5.Attract and Retain Customers
6.Product and Service Innovation
7.New markets and territories
8.Attract and Retain Personnel
9.Marketing and Sales Effectiveness
10.Increasing Enterprise Growth
IT Priorities
1.Security
2.Mobile Technology
3.High Availability/Disaster Recovery
4.Storage and Data Growth
Our development team have adopted the AGILE project management methodology. Along with new continuous testing tools they’re able to implement changes much more quickly now. They’re now finding the next barrier to agility is us, the IT operations department (the ops in DevOps). We can’t rollout software as fast as they release is. Ideally IT Operations would be able to deploy their changes within a single AGILE sprint cycle (the dev cycle).
