Spring cleaning is on its way!

Sometimes you hear from IT Support saying "the server is very slow, the required service has stopped running and the Windows updates installation failed, etc." When you logon to the server and check what went wrong, you realise the server is running out of space on C: drive and you need to delete some old files or expand the disk to fix the issue. This could become a recurring task for certain VMs. The quick and easy solution is to write a script and run it as a regular maintenance task.

When you come across orphaned DFS Namespaces in your domain environment and want to remove those either to clean up or to reuse. You will need to do it from ADSI Edit.

• Connect to Default naming context
• Navigate to CN=Dfs-Configuration,CN=System, DC=mydomain, DC=local
• Right click on the orphaned namespace and delete it

This post is about doing just that via the PowerShell Script instead of using ADSI Edit. There is an enormous risk associated with using ADSI Edit if you misclick and delete something else by mistake.

There may be the time when you need to backup your SQL Express Database on a scheduled basis and the server is running on a locked down environment with no access to the internet. In this blog post I wanted to share how I work around it using the PowerShell script to backup the Database and copy the content to the another server then back it up to the Azure Recovery Service.

There was a time when you needed to use the PowerShell script to upload your files and folders to the Azure blob storage container and you needed to maintain the folder structure. However, a few times you tried failed to achieve the result you needed.

Recently, I have been working on migrating multifactor authentication service provider from the one that runs locally to Azure AD MFA. During the process, there was the need to put all users mobile numbers from local active directory to Azure AD authentication method.