Gunr

Hey eagle00789, great program!! Used it for the first time today, worked great! Thanks!

Glad it worked. You can sometimes find useful stuff in the readme.txt, I normally don't read them myself and don't really know why I did this time!!

EDIT: Just tried this myself and it works. Just wondering if this has been tried? I have not had a chance yet, just now starting to play arround with the unattended stuff, but found this info in the readme.txt that is included with the sp2 deploy tools. * In the OEM Preinstallation Reference (Ref.chm), the functionality of the AllowConnections entry of the [TerminalServices] section in the Unattend.txt answer file has changed. If you specify the following: [TerminalServices] AllowConnections = 1 Remote Desktop will be enabled during unattended Setup. However, Remote Desktop will not be added to the Windows Firewall Exceptions list. The following entries represent the mimimum required entries in the Unattend.txt answer file to enable Remote Desktop during unattended Setup and add Remote Desktop to the Windows Firewall Exceptions list: [WindowsFirewall] Profiles = Standard (specify a user-defined profile name) [WindowsFirewall.Standard] Services = RemoteDesktop (specify a user-defined service name) [WindowsFirewall.RemoteDesktop] Type = 2 [TerminalServices] AllowConnections = 1 For details on Windows Firewall settings, see the [WindowsFirewall] sections and entries in the Unattend.txt chapter of the OEM Preinstallation Reference (Ref.chm).

If this is for a company, are you using AD? If you are, update a GPO with the new firewall settings that you require open and push it down that way. We are using that at our company and it works great. If you find later that you need another port open, modify the GPO and when the clients refresh they will get the new settings automatically.