We are in the middle of moving from 2003 servers to 2008 servers. In
the 2008 family, we have a SQL and a APP/TS server. We have gone ahead
and installed Propalms ver. 6 on the TS 2003 server and the app/ts
2008 server, but not the SQL server.
One of the Apps got installed on the wrong server (don't ask why), so
it is sitting on the SQL server. I was able to join the SQL server to
the group of servers in Propalms and was able to push the app out to
desktops.
My issue is that when you sign in to the app on the SQL server, a
screen will pop up telling you that your defalt printer has been
changed. It ususally changes to one on the server. Hyperprint is not
one of the choices.
Do I have to install propalms on the SQL to get the local window
printers to work?
Yes, in order to get HyperPrint printer option, you will have to
install Propalms App role on the SQL server. That way HyperPrint will
be installed on that server. Let me know if that answers your
questions.
Brandon Watson
Propalms Engineer
On 30 Apr, 06:24, Kris Clarke <KCLA...@BIRDSTAIRS.CA> wrote:
> We are in the middle of moving from 2003 servers to 2008 servers. In
> the 2008 family, we have a SQL and a APP/TS server. We have gone ahead
> and installed Propalms ver. 6 on the TS 2003 server and the app/ts
> 2008 server, but not the SQL server.
> One of the Apps got installed on the wrong server (don't ask why), so
> it is sitting on the SQL server. I was able to join the SQL server to
> the group of servers in Propalms and was able to push the app out to
> desktops.
> My issue is that when you sign in to the app on the SQL server, a
> screen will pop up telling you that your defalt printer has been
> changed. It ususally changes to one on the server. Hyperprint is not
> one of the choices.
> Do I have to install propalms on the SQL to get the local window
> printers to work?
Thanks for the response; I was beginning to think there was no one from
Propalms watching this site.
I went back to the re-seller / support people on this issue due to the
response time. The issue got more complex as I started following the steps
that were given to me. In the end, they have taken it back to Propalms for
them to recreate the error and to find a fix. It has been a week since it
has gone that route.
The support people I was in contact with told me to just install hyperprint
and a few other little things. Which I did and the print error is somewhat
gone. I still get a screen with "xxx printer cannot connect; your default
printer is now xxx". The funny thing is that I can never get hyperprint to
be the default. Then I have a huge issue with one system that has vista
installed (I am running XPP), and she gets a huge error screen that after a
few hundred clicks she might get something.
If you would like the emails sent between me and the "local" support people,
I can send them to you. They have screen shots and a breakdown of our
network, along with what we have tried so far.
-----Original Message-----
From: Propalms@googlegroups.com [mailto:Propalms@googlegroups.com] On Behalf
Of Brandonw
Sent: Tuesday, May 12, 2009 6:48 PM
To: Propalms
Subject: Re: defalt printer issue
Yes, in order to get HyperPrint printer option, you will have to
install Propalms App role on the SQL server. That way HyperPrint will
be installed on that server. Let me know if that answers your
questions.
Brandon Watson
Propalms Engineer
On 30 Apr, 06:24, Kris Clarke <KCLA...@BIRDSTAIRS.CA> wrote:
> We are in the middle of moving from 2003 servers to 2008 servers. In
> the 2008 family, we have a SQL and a APP/TS server. We have gone ahead
> and installed Propalms ver. 6 on the TS 2003 server and the app/ts
> 2008 server, but not the SQL server.
> One of the Apps got installed on the wrong server (don't ask why), so
> it is sitting on the SQL server. I was able to join the SQL server to
> the group of servers in Propalms and was able to push the app out to
> desktops.
> My issue is that when you sign in to the app on the SQL server, a
> screen will pop up telling you that your defalt printer has been
> changed. It ususally changes to one on the server. Hyperprint is not
> one of the choices.
> Do I have to install propalms on the SQL to get the local window
> printers to work?
Yeah, I used to Monitor this awhile ago, but have been fairly busy. I
hope to be around more so I can try and help people out. I am actually
with Tridex Systems, we are the distributor for the US. I may not know
everything, but have an abundance of knowledge already.
I would try to turn off Printing in your Connection Settings. That way
when the user connects to a session there are no printers to map and
they should not get a print dialog box at all. I would recommend
trying that first, then you will still have the HyperPrint printer
available and that is it. Let me know if that works and we can go from
there.
Thanks!
On 13 May, 05:27, "Kris Clarke" <kcla...@birdstairs.ca> wrote:
> Thanks for the response; I was beginning to think there was no one from
> Propalms watching this site.
> I went back to the re-seller / support people on this issue due to the
> response time. The issue got more complex as I started following the steps
> that were given to me. In the end, they have taken it back to Propalms for
> them to recreate the error and to find a fix. It has been a week since it
> has gone that route.
> The support people I was in contact with told me to just install hyperprint
> and a few other little things. Which I did and the print error is somewhat
> gone. I still get a screen with "xxx printer cannot connect; your default
> printer is now xxx". The funny thing is that I can never get hyperprint to
> be the default. Then I have a huge issue with one system that has vista
> installed (I am running XPP), and she gets a huge error screen that after a
> few hundred clicks she might get something.
> If you would like the emails sent between me and the "local" support people,
> I can send them to you. They have screen shots and a breakdown of our
> network, along with what we have tried so far.
> Kris
> -----Original Message-----
> From: Propalms@googlegroups.com [mailto:Propalms@googlegroups.com] On Behalf
> Of Brandonw
> Sent: Tuesday, May 12, 2009 6:48 PM
> To: Propalms
> Subject: Re: defalt printer issue
> Yes, in order to get HyperPrint printer option, you will have to
> install Propalms App role on the SQL server. That way HyperPrint will
> be installed on that server. Let me know if that answers your
> questions.
> Brandon Watson
> Propalms Engineer
> On 30 Apr, 06:24, Kris Clarke <KCLA...@BIRDSTAIRS.CA> wrote:
> > We are in the middle of moving from 2003 servers to 2008 servers. In
> > the 2008 family, we have a SQL and a APP/TS server. We have gone ahead
> > and installed Propalms ver. 6 on the TS 2003 server and the app/ts
> > 2008 server, but not the SQL server.
> > One of the Apps got installed on the wrong server (don't ask why), so
> > it is sitting on the SQL server. I was able to join the SQL server to
> > the group of servers in Propalms and was able to push the app out to
> > desktops.
> > My issue is that when you sign in to the app on the SQL server, a
> > screen will pop up telling you that your defalt printer has been
> > changed. It ususally changes to one on the server. Hyperprint is not
> > one of the choices.
> > Do I have to install propalms on the SQL to get the local window
> > printers to work?
> > thanks in advance,
> > Kris Clarke- Hide quoted text -
I have been in contact with the reseller in Canada and getting some support
from them. When I was talking to one of the sales guys, told him what I
thought about Propalms and this group (that it was a waste of time to push
end users to a group that Propalms does not even watch). He said that he was
going to be talking to the head tech guy in England and make note of this to
him.
With that being said, I thank you and others for offering suggestions and
answers to my questions!
But back to my problem...
I am now being told that I will have to install the full program (which I
was told that all I needed to do was join the server into the group) on the
server in order to get the printing problem resolved. I only spent 2-3 weeks
to get where I am now, so it looks like I have to go back to square one.
But before I do, I would like to try your suggestion. Could you give me
details on turning off printing in the connection settings? Is this on the
2008 SQL server or on the client?
-----Original Message-----
From: Propalms@googlegroups.com [mailto:Propalms@googlegroups.com] On Behalf
Of Brandon
Sent: Wednesday, May 13, 2009 12:35 PM
To: Propalms
Subject: Re: default printer issue
Yeah, I used to Monitor this awhile ago, but have been fairly busy. I
hope to be around more so I can try and help people out. I am actually
with Tridex Systems, we are the distributor for the US. I may not know
everything, but have an abundance of knowledge already.
I would try to turn off Printing in your Connection Settings. That way
when the user connects to a session there are no printers to map and
they should not get a print dialog box at all. I would recommend
trying that first, then you will still have the HyperPrint printer
available and that is it. Let me know if that works and we can go from
there.
Thanks!
On 13 May, 05:27, "Kris Clarke" <kcla...@birdstairs.ca> wrote:
> Thanks for the response; I was beginning to think there was no one from
> Propalms watching this site.
> I went back to the re-seller / support people on this issue due to the
> response time. The issue got more complex as I started following the steps
> that were given to me. In the end, they have taken it back to Propalms for
> them to recreate the error and to find a fix. It has been a week since it
> has gone that route.
> The support people I was in contact with told me to just install
hyperprint
> and a few other little things. Which I did and the print error is somewhat
> gone. I still get a screen with "xxx printer cannot connect; your default
> printer is now xxx". The funny thing is that I can never get hyperprint to
> be the default. Then I have a huge issue with one system that has vista
> installed (I am running XPP), and she gets a huge error screen that after
a
> few hundred clicks she might get something.
> If you would like the emails sent between me and the "local" support
people,
> I can send them to you. They have screen shots and a breakdown of our
> network, along with what we have tried so far.
> Kris
> -----Original Message-----
> From: Propalms@googlegroups.com [mailto:Propalms@googlegroups.com] On
Behalf
> Of Brandonw
> Sent: Tuesday, May 12, 2009 6:48 PM
> To: Propalms
> Subject: Re: defalt printer issue
> Yes, in order to get HyperPrint printer option, you will have to
> install Propalms App role on the SQL server. That way HyperPrint will
> be installed on that server. Let me know if that answers your
> questions.
> Brandon Watson
> Propalms Engineer
> On 30 Apr, 06:24, Kris Clarke <KCLA...@BIRDSTAIRS.CA> wrote:
> > We are in the middle of moving from 2003 servers to 2008 servers. In
> > the 2008 family, we have a SQL and a APP/TS server. We have gone ahead
> > and installed Propalms ver. 6 on the TS 2003 server and the app/ts
> > 2008 server, but not the SQL server.
> > One of the Apps got installed on the wrong server (don't ask why), so
> > it is sitting on the SQL server. I was able to join the SQL server to
> > the group of servers in Propalms and was able to push the app out to
> > desktops.
> > My issue is that when you sign in to the app on the SQL server, a
> > screen will pop up telling you that your defalt printer has been
> > changed. It ususally changes to one on the server. Hyperprint is not
> > one of the choices.
> > Do I have to install propalms on the SQL to get the local window
> > printers to work?
> > thanks in advance,
> > Kris Clarke- Hide quoted text -
Yeah, we do not tell our users about this group. It used to be
monitored by a Propalms Engineer in India, but he also has gotten too
busy. Also, they figure everybody should go through the appropriate
chains (IE-Reseller, distributor, etc..). Owen is the owner of
Propalms and his main focus is to make 6.0 work better, so I doubt
they will get someone on this group. If Canada support is not helping
you enough, please feel free to contact us here at Tridex Systems in
the US. We would be more than happy to help.
Now in regards to my solution.If you have an application that is on
the SQL server, and you do not have Propalms installed on that server,
then I am confused how you have that application published through
Propalms. Are you using a UNC path or something similar? To turn off
printing, login the Propalms console and navigate to the Manage |
Connection Settings page. Edit your connection setting and in the
Client Printer Sharing section, set your setting like I have shown
below. This will not redirect any of the local printers when a user
connects to a session. Please let me know if you have any questions/
concerns with this.
Client Printer Sharing
Windows 2000 - Off
Windows 2003 / 2008 - Off
Unidriver (for Propalms TSE printing only) - If vendor driver not
available
Limiting Bandwidth (for Propalms TSE printing only) - Unlimited
Compression (for Propalms TSE printing only) - Off
Allow printer properties to be remoted - Off
Select printers to remote to server - All Printers
Thanks,
Brandon
On 14 May, 06:10, "Kris Clarke" <kcla...@birdstairs.ca> wrote:
> I have been in contact with the reseller in Canada and getting some support
> from them. When I was talking to one of the sales guys, told him what I
> thought about Propalms and this group (that it was a waste of time to push
> end users to a group that Propalms does not even watch). He said that he was
> going to be talking to the head tech guy in England and make note of this to
> him.
> With that being said, I thank you and others for offering suggestions and
> answers to my questions!
> But back to my problem...
> I am now being told that I will have to install the full program (which I
> was told that all I needed to do was join the server into the group) on the
> server in order to get the printing problem resolved. I only spent 2-3 weeks
> to get where I am now, so it looks like I have to go back to square one.
> But before I do, I would like to try your suggestion. Could you give me
> details on turning off printing in the connection settings? Is this on the
> 2008 SQL server or on the client?
> I just do not want to go back to square one.
> Kris
> -----Original Message-----
> From: Propalms@googlegroups.com [mailto:Propalms@googlegroups.com] On Behalf
> Of Brandon
> Sent: Wednesday, May 13, 2009 12:35 PM
> To: Propalms
> Subject: Re: default printer issue
> Yeah, I used to Monitor this awhile ago, but have been fairly busy. I
> hope to be around more so I can try and help people out. I am actually
> with Tridex Systems, we are the distributor for the US. I may not know
> everything, but have an abundance of knowledge already.
> I would try to turn off Printing in your Connection Settings. That way
> when the user connects to a session there are no printers to map and
> they should not get a print dialog box at all. I would recommend
> trying that first, then you will still have the HyperPrint printer
> available and that is it. Let me know if that works and we can go from
> there.
> Thanks!
> On 13 May, 05:27, "Kris Clarke" <kcla...@birdstairs.ca> wrote:
> > Thanks for the response; I was beginning to think there was no one from
> > Propalms watching this site.
> > I went back to the re-seller / support people on this issue due to the
> > response time. The issue got more complex as I started following the steps
> > that were given to me. In the end, they have taken it back to Propalms for
> > them to recreate the error and to find a fix. It has been a week since it
> > has gone that route.
> > The support people I was in contact with told me to just install
> hyperprint
> > and a few other little things. Which I did and the print error is somewhat
> > gone. I still get a screen with "xxx printer cannot connect; your default
> > printer is now xxx". The funny thing is that I can never get hyperprint to
> > be the default. Then I have a huge issue with one system that has vista
> > installed (I am running XPP), and she gets a huge error screen that after
> a
> > few hundred clicks she might get something.
> > If you would like the emails sent between me and the "local" support
> people,
> > I can send them to you. They have screen shots and a breakdown of our
> > network, along with what we have tried so far.
> > Of Brandonw
> > Sent: Tuesday, May 12, 2009 6:48 PM
> > To: Propalms
> > Subject: Re: defalt printer issue
> > Yes, in order to get HyperPrint printer option, you will have to
> > install Propalms App role on the SQL server. That way HyperPrint will
> > be installed on that server. Let me know if that answers your
> > questions.
> > Brandon Watson
> > Propalms Engineer
> > On 30 Apr, 06:24, Kris Clarke <KCLA...@BIRDSTAIRS.CA> wrote:
> > > We are in the middle of moving from 2003 servers to 2008 servers. In
> > > the 2008 family, we have a SQL and a APP/TS server. We have gone ahead
> > > and installed Propalms ver. 6 on the TS 2003 server and the app/ts
> > > 2008 server, but not the SQL server.
> > > One of the Apps got installed on the wrong server (don't ask why), so
> > > it is sitting on the SQL server. I was able to join the SQL server to
> > > the group of servers in Propalms and was able to push the app out to
> > > desktops.
> > > My issue is that when you sign in to the app on the SQL server, a
> > > screen will pop up telling you that your defalt printer has been
> > > changed. It ususally changes to one on the server. Hyperprint is not
> > > one of the choices.
> > > Do I have to install propalms on the SQL to get the local window
> > > printers to work?
> > > thanks in advance,
> > > Kris Clarke- Hide quoted text -
|
