Printer Handling in MSCM 4.1

Sort:
You are not authorized to post a reply.
Author
Messages
ehartman
New Member
Posts: 3
New Member
    Has anyone been able to use MSCM4.1 with multiple printers? We have been testing over the last few weeks and the system will always print to the same physical printer: the first printer installed on the Windows server when sorted alpha. It does not matter what printer is selected in MSCM, it will still print to that one printer, even if that printer is not even the default printer for Windows on the server.... Any suggestions on how to get this to work properly? Lawson Support has not been successful in resolving this issue yet and it is holding up our go-live of MSCM 4.1.
    Ben Coonfield
    Veteran Member
    Posts: 146
    Veteran Member
      We are live on release 4.1, and we are planning to install additional label printers shortly. Please let me know if you get a fix or workaround for this as we will be in the same boat shortly.
      ehartman
      New Member
      Posts: 3
      New Member
        The problem is not with label printers. Multiple label printers is working fine for us, but multiple 'report' printers for delivery tickets and such is causing the problem.
        jmhill
        New Member
        Posts: 1
        New Member
          I could use a solution to this problem as well.
          John Henley
          Senior Member
          Posts: 3348
          Senior Member
            Are you using IP addresses or hostnames for your printers?
            Thanks for using the LawsonGuru.com forums!
            John
            ehartman
            New Member
            Posts: 3
            New Member
              Sorry for not posting this sooner, but we did figure out how to use multiple printers:
              - The printers need to be installed on the server for the account that is used for the service
              - When defining the printer in MSCM, you need to use the full path as the hostname. For example: in our environment all printers are mapped through \\print\, so this address needs to be used in the hostname in MSCM as well

              It looks like the MSCM service needs to be restarted after adding a printer to activate it.

              Hope that helps.

              Edwin
              Elliott
              New Member
              Posts: 1
              New Member
                Thanks Edward!! the restarting the MSCM service to activate the printers helped fixed our problems.
                You are not authorized to post a reply.