rsclientPrint.cab Silent Deployment??

Can anyone tell me how to deploy this client side ActiveX component to
install silently.
We obviously secure our PC's on our site and do not want the users to see a
pop up for installation (also there then could be issues with users
installation rights).
Have at least 500+ PCs to install upon
Regards
Ric PullenThis is the answer i got that worked for us. Hope you find it usefull
I guess it depends on how you locked down IE. If they can not run activeX
controls period then there is not much you can do, if they just can't
download them then you can manually install them as I describe below.
The client print control is just a COM object. You could extract the
contents and run regsvr32 on the rsclientprint.dll. There are a couple of
issues you need to be aware of though:
1) make sure all the additional files are located in the same folder as the
rsclientprint.dll
2) If we ever update the control you will need to make sure to update the
control in your script or the control may not work correctly.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Namshub" wrote:
> Can anyone tell me how to deploy this client side ActiveX component to
> install silently.
> We obviously secure our PC's on our site and do not want the users to see a
> pop up for installation (also there then could be issues with users
> installation rights).
> Have at least 500+ PCs to install upon
> Regards
> Ric Pullen
>|||Hi,
I found the link http://www.kodyaz.
com/articles/client-side-printing-silent-deployment-of-rsclientPrint.aspx
when I googled with "silent install client print reporting service"

RSClientPrint deployment question.

I have read the thread 'print active x question' posted more than a year ago
and would like to follow up...
We have an application using a webbrowser control to access reporting
services and have run into the issue of needing RSClientPrint installed
during our setup because security policies/settings may prevent the user from
installing the activex at runtime.
Has MS provided an .msi or merge module, etc. to deploy this yet? If not, is
there a definitive answer to which folder we should put the files?...is it
possible/safe to put them in Downloaded Program Files?
Thanks!
KevinHello Kevin,
We solved this problem with this small startscript in the computer group
policy.
Dim env, wshShell, fso
Set wshShell = WScript.CreateObject("WScript.Shell")
Set env = wshShell.Environment("PROCESS")
Set fso = CreateObject("Scripting.FileSystemObject")
if(Not (fso.FileExists (env("windir") & "\downloaded program
files\RSClientPrint.dll"))) Then
On Error Resume next
fso.CopyFile "\\server\rsclient\gdiplus.dll",env("windir") & "\downloaded
program files\"
On Error Resume next
fso.CopyFile "\\server\rsclient\RSClientPrint.dll", env("windir") &
"\downloaded program files\"
On Error Resume next
fso.CopyFile "\\server\rsclient\RSClientPrint.inf", env("windir") &
"\downloaded program files\"
On Error Resume next
fso.CopyFile "\\server\rsclient\RSClientPrint_1028.rll", env("windir") &
"\downloaded program files\"
On Error Resume next
fso.CopyFile "\\server\rsclient\RSClientPrint_1031.rll", env("windir") &
"\downloaded program files\"
On Error Resume next
fso.CopyFile "\\server\rsclient\RSClientPrint_1033.rll", env("windir") &
"\downloaded program files\"
On Error Resume next
fso.CopyFile "\\server\rsclient\RSClientPrint_1036.rll", env("windir") &
"\downloaded program files\"
On Error Resume next
fso.CopyFile "\\server\rsclient\RSClientPrint_1040.rll", env("windir") &
"\downloaded program files\"
On Error Resume next
fso.CopyFile "\\server\rsclient\RSClientPrint_1041.rll", env("windir") &
"\downloaded program files\"
On Error Resume next
fso.CopyFile "\\server\rsclient\RSClientPrint_1042.rll", env("windir") &
"\downloaded program files\"
On Error Resume next
fso.CopyFile "\\server\rsclient\RSClientPrint_1043.rll", env("windir") &
"\downloaded program files\"
On Error Resume next
fso.CopyFile "\\server\rsclient\RSClientPrint_1046.rll", env("windir") &
"\downloaded program files\"
On Error Resume next
fso.CopyFile "\\server\rsclient\RSClientPrint_1053.rll", env("windir") &
"\downloaded program files\"
On Error Resume next
fso.CopyFile "\\bkhl\host\stdsw\tools\rsclient\RSClientPrint_2052.rll",
env("windir") & "\downloaded program files\"
On Error Resume next
fso.CopyFile "\\bkhl\host\stdsw\tools\rsclient\RSClientPrint_3082.rll",
env("windir") & "\downloaded program files\"
wshShell.Run "REGSVR32.EXE /s """ & env("windir") & "\downloaded program
files\RSClientPrint" & """", vbMinimizedNoFocus
End if
on error resume next
Hope it helps.
Regards
Bernhard|||Bernhard,
Thanks. It answers my question that other people are having the same
problem and handling it by manually deploying the files to the Downloaded
Program Files folder.
We will most likely add the files to our existing client install. It would
be nice if Reporting Services contained a Windows Installer module for this
(hint hint).
Thanks,
Kevin
"Bernhard Weitlaner" wrote:
> Hello Kevin,
> We solved this problem with this small startscript in the computer group
> policy.
>
> Dim env, wshShell, fso
> Set wshShell = WScript.CreateObject("WScript.Shell")
> Set env = wshShell.Environment("PROCESS")
> Set fso = CreateObject("Scripting.FileSystemObject")
> if(Not (fso.FileExists (env("windir") & "\downloaded program
> files\RSClientPrint.dll"))) Then
> On Error Resume next
> fso.CopyFile "\\server\rsclient\gdiplus.dll",env("windir") & "\downloaded
> program files\"
> On Error Resume next
> fso.CopyFile "\\server\rsclient\RSClientPrint.dll", env("windir") &
> "\downloaded program files\"
> On Error Resume next
> fso.CopyFile "\\server\rsclient\RSClientPrint.inf", env("windir") &
> "\downloaded program files\"
> On Error Resume next
> fso.CopyFile "\\server\rsclient\RSClientPrint_1028.rll", env("windir") &
> "\downloaded program files\"
> On Error Resume next
> fso.CopyFile "\\server\rsclient\RSClientPrint_1031.rll", env("windir") &
> "\downloaded program files\"
> On Error Resume next
> fso.CopyFile "\\server\rsclient\RSClientPrint_1033.rll", env("windir") &
> "\downloaded program files\"
> On Error Resume next
> fso.CopyFile "\\server\rsclient\RSClientPrint_1036.rll", env("windir") &
> "\downloaded program files\"
> On Error Resume next
> fso.CopyFile "\\server\rsclient\RSClientPrint_1040.rll", env("windir") &
> "\downloaded program files\"
> On Error Resume next
> fso.CopyFile "\\server\rsclient\RSClientPrint_1041.rll", env("windir") &
> "\downloaded program files\"
> On Error Resume next
> fso.CopyFile "\\server\rsclient\RSClientPrint_1042.rll", env("windir") &
> "\downloaded program files\"
> On Error Resume next
> fso.CopyFile "\\server\rsclient\RSClientPrint_1043.rll", env("windir") &
> "\downloaded program files\"
> On Error Resume next
> fso.CopyFile "\\server\rsclient\RSClientPrint_1046.rll", env("windir") &
> "\downloaded program files\"
> On Error Resume next
> fso.CopyFile "\\server\rsclient\RSClientPrint_1053.rll", env("windir") &
> "\downloaded program files\"
> On Error Resume next
> fso.CopyFile "\\bkhl\host\stdsw\tools\rsclient\RSClientPrint_2052.rll",
> env("windir") & "\downloaded program files\"
> On Error Resume next
> fso.CopyFile "\\bkhl\host\stdsw\tools\rsclient\RSClientPrint_3082.rll",
> env("windir") & "\downloaded program files\"
> wshShell.Run "REGSVR32.EXE /s """ & env("windir") & "\downloaded program
> files\RSClientPrint" & """", vbMinimizedNoFocus
> End if
> on error resume next
>
> Hope it helps.
> Regards
> Bernhard|||Kevin,
If you have visual studio it's a pretty simple job to create an MSI to do
the same thing as Bernards script. Then you can deploy the MSI with a GPO or
whatever means you want.
Regards,
Martin.
"Kg" wrote:
> Bernhard,
> Thanks. It answers my question that other people are having the same
> problem and handling it by manually deploying the files to the Downloaded
> Program Files folder.
> We will most likely add the files to our existing client install. It would
> be nice if Reporting Services contained a Windows Installer module for this
> (hint hint).
> Thanks,
> Kevin
> "Bernhard Weitlaner" wrote:
> > Hello Kevin,
> >
> > We solved this problem with this small startscript in the computer group
> > policy.
> >
> >
> > Dim env, wshShell, fso
> > Set wshShell = WScript.CreateObject("WScript.Shell")
> > Set env = wshShell.Environment("PROCESS")
> > Set fso = CreateObject("Scripting.FileSystemObject")
> >
> > if(Not (fso.FileExists (env("windir") & "\downloaded program
> > files\RSClientPrint.dll"))) Then
> >
> > On Error Resume next
> > fso.CopyFile "\\server\rsclient\gdiplus.dll",env("windir") & "\downloaded
> > program files\"
> > On Error Resume next
> > fso.CopyFile "\\server\rsclient\RSClientPrint.dll", env("windir") &
> > "\downloaded program files\"
> > On Error Resume next
> > fso.CopyFile "\\server\rsclient\RSClientPrint.inf", env("windir") &
> > "\downloaded program files\"
> > On Error Resume next
> > fso.CopyFile "\\server\rsclient\RSClientPrint_1028.rll", env("windir") &
> > "\downloaded program files\"
> > On Error Resume next
> > fso.CopyFile "\\server\rsclient\RSClientPrint_1031.rll", env("windir") &
> > "\downloaded program files\"
> > On Error Resume next
> > fso.CopyFile "\\server\rsclient\RSClientPrint_1033.rll", env("windir") &
> > "\downloaded program files\"
> > On Error Resume next
> > fso.CopyFile "\\server\rsclient\RSClientPrint_1036.rll", env("windir") &
> > "\downloaded program files\"
> > On Error Resume next
> > fso.CopyFile "\\server\rsclient\RSClientPrint_1040.rll", env("windir") &
> > "\downloaded program files\"
> > On Error Resume next
> > fso.CopyFile "\\server\rsclient\RSClientPrint_1041.rll", env("windir") &
> > "\downloaded program files\"
> > On Error Resume next
> > fso.CopyFile "\\server\rsclient\RSClientPrint_1042.rll", env("windir") &
> > "\downloaded program files\"
> > On Error Resume next
> > fso.CopyFile "\\server\rsclient\RSClientPrint_1043.rll", env("windir") &
> > "\downloaded program files\"
> > On Error Resume next
> > fso.CopyFile "\\server\rsclient\RSClientPrint_1046.rll", env("windir") &
> > "\downloaded program files\"
> > On Error Resume next
> > fso.CopyFile "\\server\rsclient\RSClientPrint_1053.rll", env("windir") &
> > "\downloaded program files\"
> > On Error Resume next
> > fso.CopyFile "\\bkhl\host\stdsw\tools\rsclient\RSClientPrint_2052.rll",
> > env("windir") & "\downloaded program files\"
> > On Error Resume next
> > fso.CopyFile "\\bkhl\host\stdsw\tools\rsclient\RSClientPrint_3082.rll",
> > env("windir") & "\downloaded program files\"
> >
> > wshShell.Run "REGSVR32.EXE /s """ & env("windir") & "\downloaded program
> > files\RSClientPrint" & """", vbMinimizedNoFocus
> >
> > End if
> > on error resume next
> >
> >
> > Hope it helps.
> >
> > Regards
> > Bernhard|||Hello Martin
> If you have visual studio it's a pretty simple job to create an MSI to do
> the same thing as Bernards script. Then you can deploy the MSI with a GPO or
> whatever means you want.
>
This sounds very interesting. How is this possible? I have visual studio.
Regards
Bernhard|||Bernhard,
Here's the recipe...
You'll need the extracted the CabFile contents.
Then in Visual Studio:
1. Create a New Set Up Project (it's under Other Project Types). You can
call it what you like but I used RSClientPrintRedist.
2. In the Configuration properties of the SetUp Project click the
prerequisite... button and make sure none of the prerequisites are checked
and that the Create setup program to install prerequisite components is
cleared. I usually do this first because it's easy to forget and GPO
processing seems to fail if it tries to fire of an external setup file.
3. Next on the project properties set InstallAllUsers to true.
4. Under File System on Target Machine click on Applciation Folder and set
the default location to [WindowsFolder]Downloaded Program Files. You can
remove the other folders they're not needed.
5. Add all the extracted files to this folder.
6. On the properties tab for the rsclientprint.dll set the Register property
to vsdrfCOMSelfReg
7. Under the Registry on Target Machine Settings remove HKLM and KKCU
[Manufacturer Keys]
8. Under User Interface remove the Target Directory dialog screen. We don't
need to be able to specify an alternative location.
9. Build you project.
If all goes well you should have a file "RSClientPrintRedist.msi" under the
current config directoy of your project.
Creating setup kits this way is really powerful, and you don't have to be
deploying a .NET app to use them. If you have a play around with the various
options you'll see there isn't much you can't do on the target machine.
Martin
"Bernhard Weitlaner" wrote:
> Hello Martin
> >
> > If you have visual studio it's a pretty simple job to create an MSI to do
> > the same thing as Bernards script. Then you can deploy the MSI with a GPO or
> > whatever means you want.
> >
> This sounds very interesting. How is this possible? I have visual studio.
> Regards
> Bernhard|||Hello Martin,
Thank you very much.
Regards
Bernhardsql

RS deployment on load balanced servers

Could anybody offer any advice on the internal mechanics of report server?
Our server setup is as follows.
SQL Server 2000 clusters in active/passive. Load balanced web servers x 3.
One of which is a publisher with files replicated to the other two.
We'd like to set up reporting services, but need a bit of advice as to the
role of the report server.
Our plan is to set up RS on all three servers for load balancing, all
pointing to the same SQL cluster.
As I understand it, when an rdl file is deployed or uploaded to report
server, report server takes the file, breaks it down, encrypts it and
publishes it to the RS database. Is this correct? Doe RS have any other
function at this point? Are references to the reports stored on the IIS
server?
In our setup when we publish to http://abcdefg/ReportServer, our content
switches will decide which server the report is sent to. If it *doesn't* go
to our publishing server, do we need to be concerned with replication?
Also, what issues do we face RE encryption key on the three servers? We need
to ensure that they are all the same. Is this something that can be specified
during setup?
I Hope this makes sense!
JoeThis is 100% supported configuration. Search BOL for web farm (if you do not
have RS installed yet and don't have BOL then you can search the Microsoft
site for this). I don't have a web farm configuration but based on my
experience with RS this is what happens: In a web farm all the server front
ends use the same SQL Server database. So, when you deploy you only need to
deploy once and that gets the information used by the app into the database.
RS has three parts. The SQL Server database object store, and two asp.net
1.1 applications. One of the applications is core to the product, it does
all the rendering of the reports and uses the object store. The other
(Report Manager) you can consider a portal. This is optional, some people
use either URL integration or webservices and have their own front end
instead of using Report Manager.
Note that for a web farm you need to have enterprise licenses. Not only for
the SQL server cluster you have but you need an SQL Server interprise
license for each IIS server in your web farm. Every server used by RS has to
have a SQL Server license.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:0739946E-1912-4EB1-BDC1-E4DA34740295@.microsoft.com...
> Could anybody offer any advice on the internal mechanics of report server?
> Our server setup is as follows.
> SQL Server 2000 clusters in active/passive. Load balanced web servers x 3.
> One of which is a publisher with files replicated to the other two.
> We'd like to set up reporting services, but need a bit of advice as to the
> role of the report server.
> Our plan is to set up RS on all three servers for load balancing, all
> pointing to the same SQL cluster.
> As I understand it, when an rdl file is deployed or uploaded to report
> server, report server takes the file, breaks it down, encrypts it and
> publishes it to the RS database. Is this correct? Doe RS have any other
> function at this point? Are references to the reports stored on the IIS
> server?
> In our setup when we publish to http://abcdefg/ReportServer, our content
> switches will decide which server the report is sent to. If it *doesn't*
go
> to our publishing server, do we need to be concerned with replication?
> Also, what issues do we face RE encryption key on the three servers? We
need
> to ensure that they are all the same. Is this something that can be
specified
> during setup?
> I Hope this makes sense!
> Joe|||Thanks for the information Bruce. It looks like our options are to compromise
our SQL cluster by putting IIS and RS on it, something anybody with an ounce
of sense wouldn't do, or to pay MS for 3 additional enterprise liscences! I
don't know about you, but this seems to me like this is a liscence to print
money!
"Bruce L-C [MVP]" wrote:
> This is 100% supported configuration. Search BOL for web farm (if you do not
> have RS installed yet and don't have BOL then you can search the Microsoft
> site for this). I don't have a web farm configuration but based on my
> experience with RS this is what happens: In a web farm all the server front
> ends use the same SQL Server database. So, when you deploy you only need to
> deploy once and that gets the information used by the app into the database.
> RS has three parts. The SQL Server database object store, and two asp.net
> 1.1 applications. One of the applications is core to the product, it does
> all the rendering of the reports and uses the object store. The other
> (Report Manager) you can consider a portal. This is optional, some people
> use either URL integration or webservices and have their own front end
> instead of using Report Manager.
> Note that for a web farm you need to have enterprise licenses. Not only for
> the SQL server cluster you have but you need an SQL Server interprise
> license for each IIS server in your web farm. Every server used by RS has to
> have a SQL Server license.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Joe" <Joe@.discussions.microsoft.com> wrote in message
> news:0739946E-1912-4EB1-BDC1-E4DA34740295@.microsoft.com...
> > Could anybody offer any advice on the internal mechanics of report server?
> >
> > Our server setup is as follows.
> >
> > SQL Server 2000 clusters in active/passive. Load balanced web servers x 3.
> > One of which is a publisher with files replicated to the other two.
> >
> > We'd like to set up reporting services, but need a bit of advice as to the
> > role of the report server.
> >
> > Our plan is to set up RS on all three servers for load balancing, all
> > pointing to the same SQL cluster.
> >
> > As I understand it, when an rdl file is deployed or uploaded to report
> > server, report server takes the file, breaks it down, encrypts it and
> > publishes it to the RS database. Is this correct? Doe RS have any other
> > function at this point? Are references to the reports stored on the IIS
> > server?
> >
> > In our setup when we publish to http://abcdefg/ReportServer, our content
> > switches will decide which server the report is sent to. If it *doesn't*
> go
> > to our publishing server, do we need to be concerned with replication?
> >
> > Also, what issues do we face RE encryption key on the three servers? We
> need
> > to ensure that they are all the same. Is this something that can be
> specified
> > during setup?
> >
> > I Hope this makes sense!
> >
> > Joe
>
>|||Depends on your licensing how bad a hit it is. If you are doing processor
licenses then it is a pretty big hit. If all you are paying for is the
server license then not too bad (especially if you compare against Crystal
or BO). In my case my corporation has SQL Server client licenses covered for
all PCs so I have no CALs to do, just the server license. It is a different
story if you are doing processor licenses.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:EECC39FD-C9F0-4F5A-B6EE-C19D689A2F15@.microsoft.com...
> Thanks for the information Bruce. It looks like our options are to
compromise
> our SQL cluster by putting IIS and RS on it, something anybody with an
ounce
> of sense wouldn't do, or to pay MS for 3 additional enterprise liscences!
I
> don't know about you, but this seems to me like this is a liscence to
print
> money!
> "Bruce L-C [MVP]" wrote:
> > This is 100% supported configuration. Search BOL for web farm (if you do
not
> > have RS installed yet and don't have BOL then you can search the
Microsoft
> > site for this). I don't have a web farm configuration but based on my
> > experience with RS this is what happens: In a web farm all the server
front
> > ends use the same SQL Server database. So, when you deploy you only need
to
> > deploy once and that gets the information used by the app into the
database.
> > RS has three parts. The SQL Server database object store, and two
asp.net
> > 1.1 applications. One of the applications is core to the product, it
does
> > all the rendering of the reports and uses the object store. The other
> > (Report Manager) you can consider a portal. This is optional, some
people
> > use either URL integration or webservices and have their own front end
> > instead of using Report Manager.
> >
> > Note that for a web farm you need to have enterprise licenses. Not only
for
> > the SQL server cluster you have but you need an SQL Server interprise
> > license for each IIS server in your web farm. Every server used by RS
has to
> > have a SQL Server license.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Joe" <Joe@.discussions.microsoft.com> wrote in message
> > news:0739946E-1912-4EB1-BDC1-E4DA34740295@.microsoft.com...
> > > Could anybody offer any advice on the internal mechanics of report
server?
> > >
> > > Our server setup is as follows.
> > >
> > > SQL Server 2000 clusters in active/passive. Load balanced web servers
x 3.
> > > One of which is a publisher with files replicated to the other two.
> > >
> > > We'd like to set up reporting services, but need a bit of advice as to
the
> > > role of the report server.
> > >
> > > Our plan is to set up RS on all three servers for load balancing, all
> > > pointing to the same SQL cluster.
> > >
> > > As I understand it, when an rdl file is deployed or uploaded to report
> > > server, report server takes the file, breaks it down, encrypts it and
> > > publishes it to the RS database. Is this correct? Doe RS have any
other
> > > function at this point? Are references to the reports stored on the
IIS
> > > server?
> > >
> > > In our setup when we publish to http://abcdefg/ReportServer, our
content
> > > switches will decide which server the report is sent to. If it
*doesn't*
> > go
> > > to our publishing server, do we need to be concerned with replication?
> > >
> > > Also, what issues do we face RE encryption key on the three servers?
We
> > need
> > > to ensure that they are all the same. Is this something that can be
> > specified
> > > during setup?
> > >
> > > I Hope this makes sense!
> > >
> > > Joe
> >
> >
> >|||Per processor licenses!!