Guest Peter Posted March 7, 2008 Posted March 7, 2008 Hi, I am working on packaging with InstallShield (with MSI), recently we have issues of installing our package on systems that with Terminal Server installed. The systems involved is mostly W2K3 Server, if not all. Now I am assigned the issue and am looking at it, and I got many questions due to my lack of knowledge of Windows (server) systems and remote connection services. First, our product support OSs of W2K server, W2K3 server, XP, and Vista, but my search so far is that only in W2K3 server you can explicitly install (or turn on) Terminal Server, so it can become a terminal server, but not in other 3 OSs (W2K server, XP, and Vista, not considering non-microsoft, 3rd party products that can make XP/Vista terminal servers), is that true? I need confirmation from somebody with enough Windows system expertise. Second, in all of the OSs mentioned, they have 'Terminal Services' running, what is it and how is it related to 'Terminal Server' in each OS? Last, the problem we found in the installation is that (on a W2K3 server), once we turned on (or installed, whatever you name it) "Terminal Server", some of the folders were created but left empty after installation, the install still succeeded without any errors. Is there anybody with enough MSI/System knowledge can tell me why/how that happened, could that also happen on W2K/XP/Vista that don't have explicit 'Terminal Server' switch (if it doesn't, I can only focus on fix for W2K3) and possibly a good (from the point view of installation and system management) solution to fix it? Thanks in advance, Peter
Guest Lanwench [MVP - Exchange] Posted March 7, 2008 Posted March 7, 2008 Re: Question on Terminal Server Peter <Peter@discussions.microsoft.com> wrote: > Hi, > > I am working on packaging with InstallShield (with MSI), recently we > have issues of installing our package on systems that with Terminal > Server installed. The systems involved is mostly W2K3 Server, if not > all. > > Now I am assigned the issue and am looking at it, and I got many > questions due to my lack of knowledge of Windows (server) systems and > remote connection services. > > First, our product support OSs of W2K server, W2K3 server, XP, and > Vista, but my search so far is that only in W2K3 server you can > explicitly install (or turn on) Terminal Server, so it can become a > terminal server, but not in other 3 OSs (W2K server, XP, and Vista, Not quite. Win2000 Server has Terminal Services as well. It has two modes - Administration (limited to two admin logins) and Application Mode (for end users, which also requires TS licensing) W2003 Server changes things a bit. Administration mode is now just accomplished via turning on Remote Desktop, much as you do in XP. You don't install Terminal Services at all for admin use. What used to be called Application Mode in W2k Server is now just called Terminal Services. > not considering non-microsoft, 3rd party products that can make > XP/Vista terminal servers), is that true? I need confirmation from > somebody with enough Windows system expertise. > > Second, in all of the OSs mentioned, they have 'Terminal Services' > running, what is it and how is it related to 'Terminal Server' in > each OS? I think the above should clarify all that.... > > Last, the problem we found in the installation is that (on a W2K3 > server), once we turned on (or installed, whatever you name it) You have to install it - and then you have to run it & point it at a Terminal Services licensing server, which usually isn't a service you'd run on the same box. > "Terminal Server", some of the folders were created but left empty Not sure what folders you refer to. You do this in Add/Remove Programs | windows components | yaddayadda. You just tick the box to install Terminal Services and there you go. > after installation, the install still succeeded without any errors. > Is there anybody with enough MSI/System knowledge can tell me why/how > that happened, could that also happen on W2K/XP/Vista that don't have > explicit 'Terminal Server' switch (if it doesn't, They don't. Win2k has nothing like this at all - nor does XP Home. There's no remote desktop/TS hosting on those. XP Pro has Remote Desktop (this means one user can log in at a time, whether at the console or remotely). I don't yet know enough about that abomination referred to as Vista to say much but I expect all its flavors do. > I can only focus on > fix for W2K3) and possibly a good (from the point view of > installation and system management) solution to fix it? Sure, but based on your post I don't think I fully comprehend what the *problem* is, though. Note that app installs on any server running TS generally need to be done in 'install mode' - add / remove programs | browse to the installation source, rather than using plain old setup.exe from Explorer/whatnot. After you've digested all this, for more help with TS, I suggest you post in microsoft.public.windows.terminal_services. That's where the TS gurus hang out. > > Thanks in advance, > Peter
Recommended Posts