Announcement

Collapse
No announcement yet.

Windows 2003 Terminal services issue

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Windows 2003 Terminal services issue

    Hello,
    I am having issues with a windows 2003 virtual server image. I built a windows 2003 std virtual machine within xenserve. Installed updates and enable terminal server, installed few apps like office etc. created a local user account, tested it with test user account and admin user account, all works fine when i connect make terminal services session from another machine. After than, i run sysprep and converted it to a template. When i deploy a new VM using the template, the sysprep part prompts me for a computer name and local admin password, rest of the things are automated, which includes joining to a domain.
    Everything goes fine but i cant connect to the server anymore.
    Check event viewer and found that system was giving errors for 2 of the DLLs.
    C:\windows\system32\wsxica.dll
    and
    C:\windows\system32\ctxrdpwsx.dll
    and one sys file
    C:\windows\system32\drivers\wdica.sys
    I thought I will copy these files and it should work after registering the DLLs. I copied them from another 2003 server machine but I could not register the DLLs as the system could not find registry entries.
    In services msc, Terminal services service is shown as running but it cant be stopped or restarted which suggest its not actually working.
    I think I am doing something wrong while syspreping the machine while it has terminal services enabled on it. Could someone shed some light and help me out of this misery?

    Many thanks in advance.
    Regards
    Naz

  • #2
    Re: Windows 2003 Terminal services issue

    Hi,

    Please dont use sysprep when terminal server role installed on the server.
    Use sysprep and then install TS role or try to use "newsid" utility instead of sysprep.
    Best Regards,

    Yuval Sinay

    LinkedIn: https://www.linkedin.com/in/yuval14, Blog: http://blogs.microsoft.co.il/blogs/yuval14

    Comment


    • #3
      Re: Windows 2003 Terminal services issue

      Thanks yuval14, so i take it that the method i used is not recommended or supported method?

      I thought about sidgen while imaging machines with a template without sysprep but what is your take on installing presentation server 4.5 on the template and then deploying the tempalte to new VMs, change computer name/ip etc and run sidgen? or is there a prefered method to image machines with presentation server?

      Thanks

      Comment


      • #4
        Re: Windows 2003 Terminal services issue

        Please check this blogs:

        http://shannon.neutex.net/2008/07/08...th-xenappprep/

        http://t3chnot3s.blogspot.com/2009/0...-image-of.html
        Best Regards,

        Yuval Sinay

        LinkedIn: https://www.linkedin.com/in/yuval14, Blog: http://blogs.microsoft.co.il/blogs/yuval14

        Comment


        • #5
          Re: Windows 2003 Terminal services issue

          thank you very much...much appreciated...

          Comment


          • #6
            Re: Windows 2003 Terminal services issue

            Originally posted by yuval14
            Please dont use sysprep when terminal server role installed on the server.
            Use sysprep and then install TS role or try to use "newsid" utility instead of sysprep.
            I've never heard this about not using sysprep for a terminal server. In fact I've heard the opposite. Can you elaborate or provide some links to the relevant info? Thanks.

            Comment


            • #7
              Re: Windows 2003 Terminal services issue

              Originally posted by joeqwerty View Post
              I've never heard this about not using sysprep for a terminal server. In fact I've heard the opposite. Can you elaborate or provide some links to the relevant info? Thanks.
              Joeqwerty is right, that will be very usefull
              thanks

              Comment

              Working...
              X