Forked from vishnumitraha/Windows RDP login prompt.md
Created
September 2, 2024 10:16
-
-
Save nanusdad/eebd8e45b7ff82f4c20c49b2f5414ecc to your computer and use it in GitHub Desktop.
Dell Thin Client to boot directly into a Windows RDP login prompt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To configure a Dell Thin Client to boot directly into a Windows RDP login prompt, you need to adjust the settings in the `wnos.ini` file and ensure the correct configuration for Remote Desktop connections. Here are the steps to achieve this: | |
### 1. **Edit the wnos.ini File** | |
The `wnos.ini` file is used to configure various settings for the Dell Thin Client. You need to modify this file to enable direct RDP login. | |
1. **Access the wnos.ini File**: | |
- You can edit the `wnos.ini` file using the Wyse Management Suite or by manually editing it if you have access to the file system of the thin client. | |
2. **Add Necessary Settings**: | |
- Ensure the following settings are included in the `wnos.ini` file to enable direct RDP login: | |
```ini | |
; Enable RDP connection | |
autoload=2 | |
AdminMode=yes | |
Username=ConfGen | |
Password=ConfGen | |
; Enable NLA for RDP | |
SessionConfig=RDP | |
EnableNLA=Yes | |
; Specify the RDP server | |
RDP_Server=<IP or DNS name of your RDP server> | |
RDP_Port=3389 | |
; Set the broker to Microsoft for RDP | |
ConnectionBroker=Microsoft | |
``` | |
### 2. **Configure Remote Connections** | |
1. **Access System Setup**: | |
- From the desktop menu, click on "System Setup" and then select "Remote Connections" | |
2. **Broker Setup**: | |
- In the Remote Connections dialog box, go to the "Broker Setup" tab and select "Microsoft" as the broker. This will configure the thin client to use the Microsoft RDP broker | |
### 3. **Ensure RDP Settings** | |
1. **RDP Security Settings**: | |
- Ensure that the RDP server is configured to use the appropriate security settings. For example, if you are using Network Level Authentication (NLA), ensure it is enabled on both the thin client and the RDP server | |
### 4. **Example wnos.ini Configuration** | |
Here is an example of how the `wnos.ini` file might look with the necessary settings: | |
```ini | |
; General settings | |
autoload=2 | |
AdminMode=yes | |
Username=ConfGen | |
Password=ConfGen | |
; Enable RDP connection with NLA | |
SessionConfig=RDP | |
EnableNLA=Yes | |
; Specify the RDP server | |
RDP_Server=<IP or DNS name of your RDP server> | |
RDP_Port=3389 | |
; Set the broker to Microsoft for RDP | |
ConnectionBroker=Microsoft | |
; Other settings as needed | |
SignOn=yes | |
SCShowCNName=no | |
SCRemovealBahavior=1 | |
Sysmode=Classic | |
``` | |
### 5. **Apply Changes** | |
- **Save and Apply**: | |
- Save the changes to the `wnos.ini` file and apply them. If using Wyse Management Suite, deploy the updated configuration to the thin clients. | |
### Additional Considerations | |
- **Reboot the Thin Client**: | |
- After applying the changes, reboot the thin client to ensure the new settings take effect. | |
- **Test the Configuration**: | |
- Test the configuration by booting the thin client. It should now boot directly into the Windows RDP login prompt without requiring a prior login to the thin client OS | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment