Launch powershell as Admin on the workstation server where Microsoft Teams runs at start-up
Execute the following command:
Remove-ItemProperty -Path HKCU:\Software\Microsoft\Windows\CurrentVersion\Run -Name “com.squirrel.Teams.Teams”
Reboot server/workstation
If the above does not work login as an administrator and manually remove MS Teams from Add Programs and Features menu
When setting up Active Directory, the IT Administrator is given an option to select the folder path to copy the Active Directory database files to. It is advised to always to use a separate partition to save the database files instead of using the default C:\Windows\NTDS\ folder path. This provides an easier opportunity to move the Active Directory database to different location should disk space on the server dry up.
In this Step-By-Step, the lab DC currently stores its AD database files in default C:\Windows\NTDS\ folder. Steps will be detailed amidst this post to move it to a new disk added to the server. The new path it will be moved to will be E:\ADDB
Step 1: Prepping Active Directory to be moved
4. When asked if it’s okay to stop associated services, click Yes to continue.
Step 2: Moving the Active Directory database
2. Once command prompt is visible, type ntdsutil and press enter
3. Next type activate instance ntds and press enter
4. Then type files and press enter
5. In files maintenance the command to move the db is required. As mentioned earlier, the need to move the database to E:\ADDB.Type the following command to enable the move: move db to E:\ADDB
Note: Remember to use quotations (“”) should the path contain a space
6. Once the database files are successfully moved, type the following command to move the logs: move logs to E:\ADDB
7. Once the move has successfully completed, Return to the initially used services.msc and start Active Directory Domain Services stopped in Step 1
Browse to the new directory where the database files were transferred to confirm they have been transferred successfully.
Restart System.
Test logging in as a AD user.
How to modify RDS Idle Timeout and Keep alive time so users don’t get disconnected.
Logon to the RDS server in question.
Open local group policy
Win Key + R > gpedit.msc
Browse to Computer Config > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections (enable keep alive)
Select Enabled for ‘Configure keep-alive connection interval’
Then browse to Computer Config > Admin Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Session Time Limits.
Select the option shown below and enter a time limit that you see fit.
Repeat the same for the User Configuration
Browse to User Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits
Select the option shown below and enter a time limit that you see fit.
Apply gpupdate /force via Powershell or Command Prompt on the RDS Server
VMQ can cause erratic virtual machine network performance when enabled, such as latency and dropped network connections. This is especially common with Broadcom Gigabit network adapters.
This how-to will show you how to disable VMQ on your Windows host server using PowerShell.
On your host, open up a PowerShell prompt as an Administrator and enter the following command to return all of your installed NIC’s and their VMQ status:
Get-NetAdapterVmq
Next, for any NIC listed in step 1 above with VMQ set to $true, run the below command to disable VMQ. The NIC will become disconnected for approximately one second after you run this command:
Set-NetAdapterVmq -Name “NIC Name” -Enabled $False
Disable RSC with the commands below:
netsh int tcp set global rsc=disabled
Get-NetAdapterRsc | Disable-NetAdapterRsc
Get-VmSwitch | Set-VMSwitch -EnableSoftwareRsc $false
In Windows Server 2019 RDS (Not specific to RDS) users default printer may reset from the default printer they previously set each time the server is rebooted.
You will need to edit the local GPO to stop Windows from managing default printers
On the RDS Server open Local GPO Editor
Windows Key + R
gpedit.msc
Browse to User Configuration > Administrative Templates > Control Panel > Printers
Set the setting ‘Turn off Windows default printer management’ to Enabled.
Perform reboot or gpupdate /force of the RDS Server.
If the above group policy does not work it may be due to the way end users connect via their RDP shortcut, If printer redirection is turned on that default printer on their local machine will be selected rather than the default printer for their RDS user profile.
To fix this apply the below group policy setting on the RDS server.
On the Server go into the Local Group Policy Editor:
Windows Key + R
gpedit.msc
In the Local Group Policy Editor navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Printer Redirection.
Enable the Do not allow client printer redirection rule to prevent the server to install “Redirected” printers.
Perform a gpudate /force on the RDS Server or perform a reboot of the RDS Server for the GP setting to be applied.
You may want to stop end users from Accessing the Azure AD portal, as they can all view all user accounts and the email addresses associated with user accounts.
Follow the steps below to block user from Accessing Azure AD.
Login to Azure as global admin
Go the Azure AD > User Settings
Also select ‘No‘ for ‘Users can register applications’
Select ‘Yes‘ to ‘Restrict access to Azure AD administration portal’
Optional – Select ‘No‘ for ‘LinkedIn account connections’
End users will now be unable to view other users email addresses and names in Azure AD.
Firstly check to see if IIS is running via services.msc
If you attempt to start the IIS service and it fails you may get the following error message in Event Viewer
If so, navigate to C:\inetpub\history than the latest subfolder and copy the applicationHost.config and copy it to C:\Windows\system32\inetsrv\config\ then restart the World Wide Web Publishing Server and the related others, or reboot the server.
Post Windows Updates you may notice MS Exchange services and other dependent services are disabled you can check this by viewing services.msc
Execute the powershell commands below on the Exchange Server to get the services up and running.
First, we have to know which services there are and which need to have their startup type changed. I used the Get-Service cmdlet to find out. In my case, I was just interested in the Exchange Services, so I needed to filter them with the following command:
Get-Service | Where-Object { $_.DisplayName –like “Microsoft Exchange *”} | ft Name,Status
The output told me which services needed to have their startup type changed. To do that, I only had to change the entry after the last Pipe. (To change the startup type I don’t need a displayed output, but I need to change the startup type for the selected services.) This I did with the following cmdlet:
Get-Service | Where-Object { $_.DisplayName –like “Microsoft Exchange *” } | Set-Service –StartupType Automatic
The Exchange Services startup type was changed from disabled to automatic. But they were still not running. To start the services, we can use the following cmdlet:
Get-Service | Where-Object { $_.DisplayName –like “Microsoft Exchange *” } | Start-Service
After the Exchange Services have all changed their startup type and status, we are almost done. There is another service we also have to think about – IIS.
To edit the IIS Admin Service, we can follow the same concept as we did with the Exchange Services. First, we need to identify the services and set the startup type to automatic. For that, we can use this cmdlet:
Get-Service | Where-Object { $_.DisplayName –eq “IIS Admin Service” } | Set-Service –StartupType Automatic
Last but not least, we also need to start IIS Admin Service. This we can do with the following cmdlet:
Get-Service | Where-Object { $_.DisplayName –eq “IIS Admin Service” } | Start-Service
How to access Windows 10 start up location to make program run at startup or remove programs that run at startup
The All Users Startup Folder is located at the following path:
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp
The Current User Startup Folder is located here:
C:\Users\[Username]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
To find the Startup folder, the quickest way is to do the following:
There is an easy way to “bookmark” this folder.
First you need to go up one folder level. You can do this either by clicking on “Programs” in the address bar, or by clicking the up arrow to the left of the address bar.
Then, right-click the Startup folder, and choose Pin to Start:
Note also that there is actually a second Startup folder. The Startup folder above is for your user account only.
The second Startup folder is for programs that run at startup for all users on the computer. To find that Startup folder, we have to modify our Win-R trick slightly:
If the program you’re seeing at startup isn’t in either of the Startup folders, try uninstalling the program itself. Many programs run when Windows starts, but they are launched via other more complicated methods.
ISSUE:
I have a client where the Windows 10 update was installed overnight and it has broken the ability for one of the pc’s to access the other pc for file shares. It is a small network (only 2 pc’s) both running W10 Pro. The main pc can see the shares on the other pc but the one I want to see the main pc shares can only see the main pc in networks but not see any shares.
RESOLUTION:
On the sharing pc, after many attempts in getting it going, I did this and it worked:
NOTE:
Windows 10 version 1709 disables SMB 1.0
Ethernet and/or WiFi adapter sees available network,
But will not accept tcp/ip address – Will see Network icon in System Tray but will have “Exclamation mark”.
A reset of winsock and/or IP stack, may resolve the problem.
Usually – have success with a reset of winsock, then a restart.
WARNING !!!
This command must be applied at the local machine level.
Applying command on RDS network stack, will result in loss of connection for all users !!!
1. In the search box on the taskbar, type Command prompt, press and hold (or right-click) Command prompt, and then select Run as administrator > Yes.
Note:- Requires Administrator Credentials
2. At the “Administrative” Command prompt, run the following command.
Optional – Full technical Fix:-
At “Administrative” Command prompt, run the following commands in the listed order, and then check to see if that fixes your connection problem: