As mentioned earlier, we could reset the local admin password of windows instances via registry, but unfortunately that will not going to help us if we forget the user id details or we renamed the user id. And the good news is, we still will be able to logon into the system by creating one new Admin Account using AWS
Category: Microsoft
Windows, Windows Server, Microsoft 365, Word, Excel, PowerPoint, Outlook, OneNote, Teams, SharePoint, OneDrive, Edge, Bing, SQL Server, Visual Studio, Active Directory, Dynamics 365, Power BI, Power Apps, Xbox, Game Pass, Surface, Intune, Defender, Exchange, Hyper-V, .NET, Dataverse, Microsoft Copilot, Copilot Studio, Microsoft Fabric, Power Platform, Windows 11, Windows 10, WSL, Windows Subsystem for Linux
Migrated this blog to Amazon LightSail from GoDaddy
Finally, I managed to migrate my blog from GoDaddy to Amazon Lightsail, and everything looks good so far. Thanks to Amazon Lightsail for providing a static public IP (34.198.110.82). It’s really simple to migrate your blogs from any other hosting Amazon Lightsail, details information can be found here. They have very attractive pricing, which is one of the reason I
Cleanup disabled users from AD Group/s
Cleanup disabled accounts from groups is one of the most boring job, and also take lots of time. Manually it’s almost impossible to maintain. Recently I had a request to perform such task for many groups, so, I wrote a script to do it automatically on behalf of me. I am now sharing this script, hoping this might help you
Re-enabling Network Adapter in Azure VM (Resource Manager)
It is very common that sometimes we disabled the network adapter from VM to trouble shoot some network related issue, and after doing so we suddenly realize that we made a big mistake, especially if we do it on Azure VMs. Suddenly we lost all the communication to the VM, no RDP, no PowerShell, and VM got completely isolated from
Multi-Thread Super-Fast Software Inventory Scan using WSMan (PowerShell Remoting)
Recently I was asked to pull the software inventory report from multiple severs hosted in Azure, but unfortunately pulling data from WMI not allowed, only PS Remoting was enabled, so I made some changes on my previous script and used Invoke-command to pull the date for all the servers. It was easy and the most effective way to extract that report




