Showing posts with label vmware. Show all posts
Showing posts with label vmware. Show all posts

Friday, July 24, 2009

Why do you need to reboot after installing UniPrint Server?

After you install UniPrint Server, you need to reboot the system in order for it to take effect. But you don’t need to restart the system with Spool Server or Print Server. Why?

When you connect to the UniPrint Server through a remote session, for example, through Microsoft Terminal Services (MS TS) RDP or Citrix ICA connections, the UniPrint program LogScript (LogScrpt.exe) has to be launched to establish virtual channel.

When MS TS starts, it automatically launches all programs listed in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\rdpwd\StartupPrograms

The regkey StartupPrograms contains startup programs separated by commas. There should be at least one program there, and it’s rdpclip. After installing UniPrint Server, it should also contain LogScrpt.

The program rdpclip.exe is a Microsoft program used by TS. This program resides in %windir%\System32 (usually it’s C:\WINDOWS\System32), so it should not be a problem for Windows to find this program.

On the other hand, the LogScript program (LogScrpt.exe) resides usually in C:\Program Files\UniPrint Suite\Common Files. But how does Windows know where to find it?

One of the ways that Windows finds a program is to look at the environment variable PATH in the system table, which contains a list of paths for finding programs separated by semi-colons. A typical PATH, after installing UniPrint Server, may look like this:
C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\UniPrint Suite\Common Files

Since PATH is a system level environment variable, its content is set only at system startup. Any changes to its content after system startup won’t take effect. For the changes to take effect, one has to simply reboot the machine.


Click here to see a complete list of articles


To contact us: uniprint.user@gmail.com.

 


Friday, July 17, 2009

UniPrint products overview

With the current buzzword of Virtual Desktop Infrastructure (VDI), or in the more arcane IT vocabulary of Server-based Computing (SbC), you won't miss this keyword: UniPrint. Why? Simply because they are a key player.

Their products enhance VDI printing and SbC printing in Citrix as well as Microsoft terminal Server platforms. Their products are indispensable in helping system administrators manage and solve printing problems.

The following are their product offerings:

  • UniPrint Server – A core product of UniPrint for fat-client printing. A special version, UniPrint Terminal Server Edition, works specifically in the Microsoft Terminal Server platform, but not in the Citrix platform.

  • UniPrint Gateway Edition – The core product with extended capability for thin-client printing. There is also a special version, UniPrint Gateway Terminal Server Edition, that works specifically in the Microsoft Terminal Server platform, but not in the Citrix platform.

  • UniPrint VDI Edition – This product tailors specifically for printing in a Virtual Desktop Infrasturcture (VDI) environment such as that offered by VMware.

  • UniPrint Host Edition – This product enables flexible printing from non-Windows host systems (e.g., mainframes and legacy systems as well as Unix boxes) to Windows desktops.


Click here to see a complete list of articles


To contact us: uniprint.user@gmail.com.