Sometimes when you delete a VM, you will see in vCenter the machine doesn’t get removed fully.
You will see ServerName (orphaned).
There are a few ways to attempted to delete the VM:
Deleting an orphaned virtual machine when the Remove option is not available (1011468):
How to delete VM’s from vSphere Client if they are stuck?
Use PowerCLI to Delete VM
- Open PowerShell as Administrator
- Ensure the PowerCLI is imported:
- Connect to vCenter:
Connect VI-Server <FQDN of vCenter>
- Display list of VMs:
- Delete VM:
Remove-VM <VM to delete>
NB: If the VM name has spaces, then make sure you surround the name in quotes.
Azure Service Fabric is a distributed systems platform that makes it easy to package, deploy, and manage scalable and reliable microservices and containers. Service Fabric also addresses the significant challenges in developing and managing cloud native applications. Developers and administrators can avoid complex infrastructure problems and focus on implementing mission-critical, demanding workloads that are scalable, reliable, and manageable. Service Fabric represents the next-generation platform for building and managing these enterprise-class, tier-1, cloud-scale applications running in containers.
Follow this link for more information.
Ever wanted to know when a Microsoft Product is due to expire… check out this really handy search tool:
We have used the WordPress Duplicator Plugin many times to backup sites and move them to new hosting solutions.
However, on occasion we find special characters in pages and posts, such as Â or Ã. So here is a simple way to remove them.
Log onto your mySQL DB and check if you have any special chars:
SELECT * FROM 'wp_posts' where 'post_content' like '%Â%'
If you do, then use this simple UPDATE command to replace them:
UPDATE wp_posts SET post_content = REPLACE (post_content, 'Â', '');
Hope that helps.
How to Scale Websites
For increased performance and throughput for your websites on Microsoft Azure, you can use the Azure Management Portal to scale your Web Hosting Plan mode from Free to Shared, Basic, or Standard.
Scaling up on Azure Websites involves two related actions: changing your Web Hosting Plan mode to a higher level of service, and configuring certain settings after you have switched to the higher level of service. Both topics are covered in this article. Higher service tiers like Standard mode offer greater robustness and flexibility in determining how your resources on Azure are used.
Changing modes and configuring them is easily done in the Scale tab of the management portal. You can scale up or down as required. These changes take only seconds to apply and affect all websites in your Web Hosting Plan. They do not require your code to be changed or your applications to be redeployed.
NB: You cannot use auto scale in Free mode. Auto scale is only available in Shared, Basic and Standard mode. Changing your Web Hosting Plan mode to a higher level of service will probably increase your monthly charges. For charges, see Websites Pricing Details
Read more at Microsoft Azure
The service started having issues just before 1am UK time, and services are only now slowly returning to normal.
Microsoft confessed that multiple regions were affected by the “service interruption”.
Customers around the world using Azure storage, virtual machines, a number of SQL products and Active Directory, among other services, were confronted by the lengthy outage.
By 7am UK time this morning, Microsoft claimed to have revived its cloud platform.
It’s the second major outage to have hit Redmond’s Azure service in the past three months. In August, it had a similar sit-down, much to the frustration of it’s customers
Read more at The Register
Microsoft Azure enables you to script and automate virtually everything using Windows PowerShell or the cross platform command line tools, which can be used from Windows, Mac, or Linux.
Read more at Microsoft Azure Script Center
In the past you’ve needed a separate IP address for each SSL website. With the introduction of Server Name Indication (SNI), you can bind many SSL certificates to a single IP.
What is Server Name Indication (SNI)?
SNI stands for Server Name Indication and is an extension of the TLS protocol. It indicates which hostname is being contacted by the browser at the beginning of the ‘handshake’-process. This allows a server to connect multiple SSL Certificates to one IP address.
How SNI works
Browsers that support SNI will immediately communicate the name of the website the visitor wants to connect with during the initialisation of the secured connection, so that the server knows which certificate to send back. This allows browsers/clients and servers supporting SNI to connect multiple certificates for multiple domainnames to one IP address.
SNI is not common practice yet, because some older browsers/systems cannot support the technique. This is because the SSL/TLS library can be transmitted as part of the request and as part of the operating system. Some browsers support SNI on all operating systems, but a small number only support SNI on specific operating systems.
Browsers that offer support for SNI:
- Internet Explorer 7 or higher, on Windows Vista or newer. (Does not work on Windows XP and Internet Explorer 8)
- Mozilla Firefox 2.0 or higher
- Opera 8.0 or higher (the TLS 1.1 protocol must be implemented)
- Opera Mobile, version must be at least 10.1 beta on Android
- Google Chrome (Windows Vista or newer, Windows XP requires Chrome 6 or higher, OS X 10.5.7 or newer requires Chrome 5.0.342.1 or higher)
- Konqueror/KDE 4.7 or higher
- MobileSafari for Apple iOS 4.0 or newer
- Android standard browser on Honeycomb (v3.x) or higher
- Windows Phone 7
The following servers that support SNI:
- Apache 2.2.12 or higher, must use mod_ssl
- Apache Traffic Server 3.2.0 or higher
- Cherokee, must have TLS support implemented
- F5 Networks Local Traffic Manager, version 11.1 or higher
- G-WAN Web app. Server, must use OpenSSL with SNI support
- Apache Tomcat on Java 7 or higher
- Microsoft Internet Information Server IIS 8
- Saetta Web Server via OpenSSL
- Citrix NetScaler 9.2 or higher
- HAProxy 1.5 or higher