Remote desktop services need to enable for Pip session to Initialize.
Basic Configuration To Check During Pip Session
Step 1: Remote Desktop Protocol (RDP) sessions can have multiple instances with the same user account. This may be undesirable or misleading if access to the machine is primarily remote. Connection to the RDP session can be achieved through the command line and constrained to the “console” session, which would be the locally accessible session.
- Acquire access to the Windows command line (cmd.exe). This can be done by pressing the Windows key and the r key on the keyboard, then by typing
- cmd and pressing enter.
- Next, type the following:
- mstsc /console /V:address
- If unable to have the session, check the below Registry key.
- Location In Regedit Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Terminal Server Client and Check ConnecttoChildsession key with value 1 If not Present Create the same key.
Step 2: Check the Below key,
- Location In Regedit Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server with value fDenyTSConnections
Perform the following step to enable Remote Desktop using C script:
- Type cscript c:\windows\system32\scregedit.wsf /ar 0 and press Enter to enable Remote Desktop.
Note: A value of 0 indicates Remote Desktop is enabled and a value of 1 indicates it is disabled when querying the fDenyTSConnections registry key.
Perform the following step to determine if Remote Desktop is enabled.
- Type reg "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /f fDenyTSConnection and press Enter to query the registry key.
Step 3: Go to the service.MSc and check the remote desktop services are open. The below services need to be enabled
Step 4: Check the Local Policy >> Administrative template > Windows Component > Remote Desktop service > Connections
Check if any policy is set for the connection. need to be an Automatic connection without any configuration.
Step 5: Check for the Port 3389 need to be open
- Check for the Inbound and outbound for port 3389
- If the issue persists, ask the internal team to enable the Local session for the same user - machine .