Welcome to ISAserver.org

Client Deploy Problems...

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 Firewall] >> Firewall Client >> Client Deploy Problems...

Page: [1]

Message

<< Older Topic Newer Topic >>

Client Deploy Problems... - 18.Aug.2004 9:12:00 PM

cytranic

Posts: 33
Joined: 18.Aug.2004
Status: offline

I have a windows 2000 domain.

The ISA server is connected to the domain.

None of my users are local power users or admins of their machines..

The problem I am having is deploying the client. I setup everything in GPO to assign the client to the users. When a user logs in, I can see where is says installing the firewall client but it never appears in the process, or the task bar.

It also doesnt set my proxy information in the Internet Exploere options...

Do my users need to be powerusers/admins of their machine to be able to send them the client via GPO???

Do I need to set another GPO that enables them to install the firewall client...I'm sorta lost...

Post #: 1

Featured Links*

RE: Client Deploy Problems... - 19.Aug.2004 7:02:00 PM

tshinder

Posts: 47663
Joined: 10.Jan.2001
From: Texas
Status: offline

Hi C,

Assign to *machines* never assign to users.

HTH,
Tom

(in reply to cytranic)

Post #: 2

RE: Client Deploy Problems... - 19.Aug.2004 10:00:00 PM

cytranic

Posts: 33
Joined: 18.Aug.2004
Status: offline

Will the users need local admin rights? Or will the firewall be installed before the user ever logs in...

Either way its not working...At least not the way I'm doing it...It doesnt seem to hard..

(in reply to cytranic)

Post #: 3

RE: Client Deploy Problems... - 25.Aug.2004 9:22:00 PM

JBakels

Posts: 78
Joined: 4.Jan.2002
From: Bradenton, FL USA
Status: offline

Make sure you are assigning it the your computers. When you assign the group policy the computers must be in the OU or sub OU.

Here is an example:

OU=Domain (default Domain Policy)
SUB OU=MAIN (Main Group Policy)
SUB OU=XP Systems (XP-Systems Policy)
SUB OU=Accounting XP Systems (Accounting Software Deployment Policy)

All Accounting Computers are in the Accounting XP Systems.
The Group Policy "Accounting Software Deployment Policy" has the firewall client assigned in the computer section of the policy.

Hope this helps!

P.S.
Clients do not need admin rights.
The software should deploy before they login.

[ August 25, 2004, 09:27 PM: Message edited by: Jerry ]

(in reply to cytranic)

Post #: 4

RE: Client Deploy Problems... - 8.Sep.2004 4:49:00 AM

cytranic

Posts: 33
Joined: 18.Aug.2004
Status: offline

HI Just following up.

Thanks to the above poster, I know understand that you need a seprate OU for computers. I named mine WORKSTATION COMPUTERS and applied a computer GPO and everything went perfect.

THanks again!

(in reply to cytranic)

Post #: 5

RE: Client Deploy Problems... - 8.Sep.2004 4:10:00 PM

tshinder

Posts: 47663
Joined: 10.Jan.2001
From: Texas
Status: offline

quote:
Originally posted by cytranic:
Will the users need local admin rights? Or will the firewall be installed before the user ever logs in...

Either way its not working...At least not the way I'm doing it...It doesnt seem to hard..

Hi Cytranic,

If you assign to machines, the Firewall client software is installed before the user logs on, so the user doesn't need to be an admin.

HTH,
Tom

(in reply to cytranic)

Post #: 6

RE: Client Deploy Problems... - 8.Sep.2004 4:22:00 PM

tshinder

Posts: 47663
Joined: 10.Jan.2001
From: Texas
Status: offline

quote:
Originally posted by Jerry:
Make sure you are assigning it the your computers. When you assign the group policy the computers must be in the OU or sub OU.

Here is an example:

OU=Domain (default Domain Policy)
SUB OU=MAIN (Main Group Policy)
SUB OU=XP Systems (XP-Systems Policy)
SUB OU=Accounting XP Systems (Accounting Software Deployment Policy)

All Accounting Computers are in the Accounting XP Systems.
The Group Policy "Accounting Software Deployment Policy" has the firewall client assigned in the computer section of the policy.

Hope this helps!

P.S.
Clients do not need admin rights.
The software should deploy before they login.

Hi Jerry,

Good point! You definitely don't want to assign the Firewall client to Servers, so you do need to create an OU for those machines you want the Firewall client software installed on.

Thanks!
Tom

(in reply to cytranic)

Post #: 7