Posts

Remote Desktop to a PC not joined to AD domain

Image
 In cases where you are in an Active Directory environment and you need to remote to a desktop that's not joined to that directory, or is a member of an Azure directory, the login prompt usually leads to an error. Remote machine is AAD joined. IF you are signing in to your work account, try using your work email address: There are a couple of options:  Log in via Azure web (will required 2FT if enabled) Present the login AFTER the RDC connection Here are the steps: 1. Login via Azure On Remote Desktop, click Show Options, Advanced tab Check "Use a web account to sign in to the remote computer" Click Connect Your organisation's Azure SSO login screen will appear.  2. Present the login screen AFTER connecting to RDC Go to your Documents folder and look for .rdp that you are using Right-click this file and edit using Notepad At the bottom of the file, add this line: enablecredsspsupport:i:0 authentication level:i:2 Save the file. Open Remote Desktop and connect to the co...

Missing Taskbar icons in Win11

 If some of the taskbar icons turned blank or white, open a Command Prompt as Administrator, then run these commands ie4uinit.exe -show taskkill /IM explorer.exe /F DEL /A /Q "%localappdata%\IconCache.db" DEL /A /F /Q "%localappdata%\Microsoft\Windows\Explorer\iconcache*" explorer.exe

Cisco ASA5510: Can't open ASDM on Windows 10 or 11

If you can't open it due to java: Install Java 7 Go to Control Panel and search of Java. Open Java. Go to Security tab In the Exception Site List, add the url if your firewall (eg, https://192.168.0.1) Click OK to save If you encounter the message"this app can't run on your PC", do the following:  Go to C:\Users\{username}\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Cisco ASDM-IDM Launcher Right-click the Cisco ASDM-IDM Launcher shortcut, then click Properties In the Target box, change the path to wscript.exe to: C:\Windows\System32\wscript.exe   invisible.vbs run.bat Click OK to save. Run ASDM again

Convert GoDadddy Cert to PFX + Private Key for Apache

Use these steps to convert your Godaddy-issued Certificate (CRT or P7B) for use with Apache (requires PFX + Private Key). Important Note: The certificate request most be down on an IIS server, so it's easier to import it back in the server. Other, the first part of the guide will have to be done using the Certificates MMC. Convert the files to password-protected PFX Open IIS on the server there the CSR was created Go to the Server Node, and open Server Certificates On the right pane, choose Complete Certificate Request and choose the CRT of P7B file from GoDaddy, assign a simple name. Once done, right-click the certificate and choose Export Assign a filename for the Export Assign a password  Click Export to create the PFX file Convert the password-protected PFX file to PFX + private key Go to the Apache server and open a command prompt If needed, add the path then openssl.exe file to the PATH environmental variable by issuing this command: PATH=%PATH%;{folder location of openssl.ex...

Upgrade Windows 11 Home to Pro

 Found this on Reddit Open up Powershell Type  irm https://get.activated.win | iex  and hit enter Disconnect from the Internet Enter the "Extras menu" Enter the "Change Windows Edition menu" . Choose "Professional" (You can choose other editions as well) Choose the first method Confirm it and wait a few minutes until your laptop reboots After this you can activate Windows via Settings -> Activation Settings

Win10 computer can't connect to Win2003 share because of SMB1

 We had an incident today where a new laptop with Windows 10 Pro couldn't connect to the folder share on one of our servers. The server is an old Windows 2003 Standard. After some research, I found that SMB 1.0 is no longer included in the newer releases of Windows 10. Unfortunately for us, we're not ready to upgrade the server yet, so the fix had to be done on the client.  Here's the solution I found on the web. This should be done on the Windows 10 computer. Press Windows key + R  Type: optionalfeatures.exe, Enter Scroll down to SMB 1.0/CIFS File Sharing Support Check "SMB 1.0/CIFS Client" Click OK  Restart the computer And done!

Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine

Image
I had an issue today where an Office update caused my C# applications to stop connecting to my access database. I suddenly started getting the error: Here's how to fix it. First, confirm that you do not have Office 12.0 OLE DB Provider by opening up PowerShell and running this command (New-Object system.data.oledb.oledbenumerator).GetElements() | select SOURCES_NAME, SOURCES_DESCRIPTION This screen shot was taken after I fixed my computer. It shows ACE.OLEDB.12.0, 15.0, and 16.0. If you don't have these, run the Access 2016 runtime installer from: http://www.microsoft.com/en-us/download/details.aspx?id=50040