Jump to content

davbroom

Member
  • Posts

    2
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Everything posted by davbroom

  1. On Windows Server 2003 in Terminal Services Configuration Manager, RCP-Tcp properties. I am trying to set the encyption level. However, the option is greyed out and displays the value 'High'. Based on previous knowledege, this should associate with the registry key HKLM\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\MinEncryptionLevel this value is set to 2. Could someone please explain why the menu options are greyed out and if possible make it available? Also why is the registry setting set to a value of 2 and not 3 (as the GUI display the encryption level as high) ? Thanks in advance
  2. Having performed several unattended builds in my time and come across various issues have now come across something new and require a little assistance. I have a WindowsXP SP2 unattended build that have used several times before due to new hardware I have had to modifiy the driver set (updating the SIF file and txtsetup.oem file). As the windows installation process kicks in I recieve the following error :- 'File caused an unexpected error(0) at line 2166 in d:\xpsp\base\boot\setup\oemdisk.c. Press any key to continue' If I press any key, the build continues through ok (ie. my new SATA drivers are working fine). (1) Can anyone explain what to look for with this error, the build works ok. I have searched my SIF, OEM file, INF files etc and none of these go up to line 2166. (2)What is error(0) (3)What exactly is oemdisk.c. where does this come from? and where does the d: drive come from? If I understand how this iworks I may be able to pinpoint my problem. Thanks in advance, if you would like me to supply any additional detail please just ask.
×
×
  • Create New...