Sign in with
Sign up | Sign in
Your question

Public non MSI applications. ZAP files

Last response: in Windows 2000/NT
Share
Anonymous
September 22, 2004 4:27:25 PM

Archived from groups: microsoft.public.win2000.group_policy (More info?)

Hello,
Few months back, I posed a question in this "FORUM" on
how to install an application that does not have an .MSI
file, such as WinZip, and the solution suggested by
experts, or person's who replied to me was the use of
script.

Well... In my company, no scripts are allowed to run, no
third-party solutions, no remote admin software, thus
I am forced to use GPO. I can't use SMS or other MS
costly applications! I asked for the ZAP file, that is the
solution provided by Microsoft for applications that
do not come packaged with MSI files.

I'm here to auto-answer my own question. YES there is a
solution, and this misterious ZAP file is nothing but a
little, naive TXT file!

Example:

In your GPO, you defined the application path on a server
to be \\SERVER_NAME\SHARED_FOLDER

Now put your software folder in this shared folder on the
server, ex: WinZip, this makes it
\\SERVER_NAME\SHARED_FOLDER\WinZip

the WinZip setup file(s) must be in this folder.
All you have to do is run your notepad, and write the
following:

[Application]
FriendlyName = WinZip 9.0 (you can write whatever here)
SetupCommand
= ""\\SERVER_NAME\SHARED_FOLDER\WinZip\Setup.exe""

You are DONE! Save the txt file as FileName.ZAP in that
shared folder, then publish or assign the application
selecting the ZAP extention instead ot the default MSI
extention!!!

NOTE:
THE DOUBLE QUOTES ARE MANDATORY! IF YOUR APPLICATION SETUP
SUPPORTS COMMAND SWITCHES, THEN THE SYNTAX OF THE ZAP FILE
BECOMES:

[Application]
FriendlyName = My Company Application
SetupCommand
= ""\\Server\Share\Application\Setup.exe" /SWITCH"

I tried it and it works perfectly!!!

Ihab
Let me know if this works for you guys!
Anonymous
September 24, 2004 2:38:02 AM

Archived from groups: microsoft.public.win2000.group_policy (More info?)

Ihab,

I have never used a .zap file but am naturally familiar with it. Thank you
for posting an answer to your own question. It looks to be very good and
extremely useful for those in similar situations.

I am curious, though, why you are not allowed to run scripts in your
environment and why you are not allowed to install any remote Admin tools?
You do not need to answer if you do not want. I am simply curious about
this type of environment and what leads to such policies.

Cary

"Ihab Abedrabbo" <ihab17@hotmail.com> wrote in message
news:03a701c4a0da$30b290a0$a301280a@phx.gbl...
>
> Hello,
> Few months back, I posed a question in this "FORUM" on
> how to install an application that does not have an .MSI
> file, such as WinZip, and the solution suggested by
> experts, or person's who replied to me was the use of
> script.
>
> Well... In my company, no scripts are allowed to run, no
> third-party solutions, no remote admin software, thus
> I am forced to use GPO. I can't use SMS or other MS
> costly applications! I asked for the ZAP file, that is the
> solution provided by Microsoft for applications that
> do not come packaged with MSI files.
>
> I'm here to auto-answer my own question. YES there is a
> solution, and this misterious ZAP file is nothing but a
> little, naive TXT file!
>
> Example:
>
> In your GPO, you defined the application path on a server
> to be \\SERVER_NAME\SHARED_FOLDER
>
> Now put your software folder in this shared folder on the
> server, ex: WinZip, this makes it
> \\SERVER_NAME\SHARED_FOLDER\WinZip
>
> the WinZip setup file(s) must be in this folder.
> All you have to do is run your notepad, and write the
> following:
>
> [Application]
> FriendlyName = WinZip 9.0 (you can write whatever here)
> SetupCommand
> = ""\\SERVER_NAME\SHARED_FOLDER\WinZip\Setup.exe""
>
> You are DONE! Save the txt file as FileName.ZAP in that
> shared folder, then publish or assign the application
> selecting the ZAP extention instead ot the default MSI
> extention!!!
>
> NOTE:
> THE DOUBLE QUOTES ARE MANDATORY! IF YOUR APPLICATION SETUP
> SUPPORTS COMMAND SWITCHES, THEN THE SYNTAX OF THE ZAP FILE
> BECOMES:
>
> [Application]
> FriendlyName = My Company Application
> SetupCommand
> = ""\\Server\Share\Application\Setup.exe" /SWITCH"
>
> I tried it and it works perfectly!!!
>
> Ihab
> Let me know if this works for you guys!
September 25, 2004 9:33:46 AM

Archived from groups: microsoft.public.win2000.group_policy (More info?)

Cary,
Thanks for your comments. Unfortunately, when working
in IT related business, you are not the only one involved
in decision making. In my situation, I am surrounded by
quasi-IT personnel that unfortunately command the
situation.

When I first used a logon script, everything was going
perfet for 3 days, untill I saw the Delegated Commercial
Administrator (of a company that has more than 20,000
dependents, and for privacy I won't write it's name)
behind my shoulders, a bit upset of that black window
(the command prompt when a vbs script is executed)
appearing on his computer everytime he logs on!
Of course, I could hide this screen or any application
during the logon progress, but I didn't think that
the DCA would react like this, and that EVERYTHING of this
kind should be prohibited!

When working in IT, ignorant and arrogant HR, Directors
and responsibles are those who command! So you have got
to re-arrange your plans!

I wish that problems in IT are only those related to IT
or just like the fancy IT book-related questions are!

No remote admin programs are allowed because they do not
want to spend even a cent to buy the cheapest program. The
employment situation here is going bad, many people were
just fired because of company financial capacities. Besides
in the past DameWare was used for a while (that wasn't
even a registered version!), and then a tech-person
finished up in remote controlling a PC without the
authorization of the user who was actually one of the admin
board of this company!

In my own company, for examle, we had to remove our SMS
because of the continuous complains of directors of several
other departments!

Ihab
Anonymous
September 25, 2004 1:25:43 PM

Archived from groups: microsoft.public.win2000.group_policy (More info?)

Ihab,

I understand that the IT department is not the only one involved in the
decisions. You usually have a Financial person and an Operations person
involved. It is typically the job of the IT Director ( or whatever the
title is.... ) to present all the facts for the Financial and Operations
people in such a way that they understand the needs and the solutions and to
recommend a solution.

If the company is 'super cheap' then you have a decision to make. If other
people are involved ( the Delegated Commercial Administrator ) that possibly
should not be ( why is this person a 'Delegated Commercial Administrator'
and what does that really mean? ) then your decision should be very clear.

I would have a very difficult time working someplace where the secretary is
able to dictate policy ( The "oh, that color is pretty! Let's do that!" or
the "I do not want to have to wait for anything. It should just always
work!" syndrome ). I have seen this before and it is usually very
indicative of much larger problems.

Sounds like you are in a tough situation.

Hope that you're able to find an acceptable solution.

Cary

"Ihab" <anonymous@discussions.microsoft.com> wrote in message
news:1ee601c4a2fb$e689fb70$a301280a@phx.gbl...
> Cary,
> Thanks for your comments. Unfortunately, when working
> in IT related business, you are not the only one involved
> in decision making. In my situation, I am surrounded by
> quasi-IT personnel that unfortunately command the
> situation.
>
> When I first used a logon script, everything was going
> perfet for 3 days, untill I saw the Delegated Commercial
> Administrator (of a company that has more than 20,000
> dependents, and for privacy I won't write it's name)
> behind my shoulders, a bit upset of that black window
> (the command prompt when a vbs script is executed)
> appearing on his computer everytime he logs on!
> Of course, I could hide this screen or any application
> during the logon progress, but I didn't think that
> the DCA would react like this, and that EVERYTHING of this
> kind should be prohibited!
>
> When working in IT, ignorant and arrogant HR, Directors
> and responsibles are those who command! So you have got
> to re-arrange your plans!
>
> I wish that problems in IT are only those related to IT
> or just like the fancy IT book-related questions are!
>
> No remote admin programs are allowed because they do not
> want to spend even a cent to buy the cheapest program. The
> employment situation here is going bad, many people were
> just fired because of company financial capacities. Besides
> in the past DameWare was used for a while (that wasn't
> even a registered version!), and then a tech-person
> finished up in remote controlling a PC without the
> authorization of the user who was actually one of the admin
> board of this company!
>
> In my own company, for examle, we had to remove our SMS
> because of the continuous complains of directors of several
> other departments!
>
> Ihab
>
Anonymous
October 12, 2004 1:39:31 PM

Archived from groups: microsoft.public.win2000.group_policy (More info?)

I just wanted to thank you as well Ihab, this is exactly what I'm looking
for.

Chris

"Ihab Abedrabbo" <ihab17@hotmail.com> wrote in message
news:03a701c4a0da$30b290a0$a301280a@phx.gbl...
>
> Hello,
> Few months back, I posed a question in this "FORUM" on
> how to install an application that does not have an .MSI
> file, such as WinZip, and the solution suggested by
> experts, or person's who replied to me was the use of
> script.
>
> Well... In my company, no scripts are allowed to run, no
> third-party solutions, no remote admin software, thus
> I am forced to use GPO. I can't use SMS or other MS
> costly applications! I asked for the ZAP file, that is the
> solution provided by Microsoft for applications that
> do not come packaged with MSI files.
>
> I'm here to auto-answer my own question. YES there is a
> solution, and this misterious ZAP file is nothing but a
> little, naive TXT file!
>
> Example:
>
> In your GPO, you defined the application path on a server
> to be \\SERVER_NAME\SHARED_FOLDER
>
> Now put your software folder in this shared folder on the
> server, ex: WinZip, this makes it
> \\SERVER_NAME\SHARED_FOLDER\WinZip
>
> the WinZip setup file(s) must be in this folder.
> All you have to do is run your notepad, and write the
> following:
>
> [Application]
> FriendlyName = WinZip 9.0 (you can write whatever here)
> SetupCommand
> = ""\\SERVER_NAME\SHARED_FOLDER\WinZip\Setup.exe""
>
> You are DONE! Save the txt file as FileName.ZAP in that
> shared folder, then publish or assign the application
> selecting the ZAP extention instead ot the default MSI
> extention!!!
>
> NOTE:
> THE DOUBLE QUOTES ARE MANDATORY! IF YOUR APPLICATION SETUP
> SUPPORTS COMMAND SWITCHES, THEN THE SYNTAX OF THE ZAP FILE
> BECOMES:
>
> [Application]
> FriendlyName = My Company Application
> SetupCommand
> = ""\\Server\Share\Application\Setup.exe" /SWITCH"
>
> I tried it and it works perfectly!!!
>
> Ihab
> Let me know if this works for you guys!
!