#183150 - 2007-12-02 04:05 PM
Installing packages via GPO Startup script.
|
Shawn
Administrator
Registered: 1999-08-13
Posts: 8611
|
Moved discussion of this to here.
So Witto, your function here uses this syntax in your INI file:
;NetworkID ; Network or networks where computer should be to allow software installation ; The format of the list of networks should be build like this ; xxx.xxx.xxx.xxx/yy;xxx.xxx.xxx.xxx/yy;xxx.xxx.xxx.xxx/yy ; where xxx.xxx.xxx.xxx is the NetworkID and yy is the Net Mask ; preceeding zero's should not be used ; In example: ; NetworkID=192.168.1.0/24;172.16.0.0/27
I'm not a network weenie - can you explain how this mask works ... does that mean apply the package to machines with the IP 192.168.1.0 to .24 or is that "24" more of a binary mask ?
[edit]
So if I wanted all ip with 192.168.1.* one would use 255 as that second number ?
-Shawn
Edited by Shawn (2007-12-02 04:09 PM)
|
Top
|
|
|
|
#183154 - 2007-12-02 04:41 PM
Re: Installing packages via GPO Startup script.
[Re: Shawn]
|
Witto
MM club member
Registered: 2004-09-29
Posts: 1828
Loc: Belgium
|
The net mask can be written in decimal numbers or in binary numbers. If you write it binary, you just tell how much 1's you see. Try to make it clear like this:
/20 = 11111111.11111111.11110000.00000000 = 255.255.240.0
/21 = 11111111.11111111.11111000.00000000 = 255.255.248.0
/22 = 11111111.11111111.11111100.00000000 = 255.255.252.0
/23 = 11111111.11111111.11111110.00000000 = 255.255.254.0
/24 = 11111111.11111111.11111111.00000000 = 255.255.255.0
/25 = 11111111.11111111.11111111.10000000 = 255.255.255.128
/26 = 11111111.11111111.11111111.11000000 = 255.255.255.192
/27 = 11111111.11111111.11111111.11100000 = 255.255.255.224
/28 = 11111111.11111111.11111111.11110000 = 255.255.255.240
/29 = 11111111.11111111.11111111.11111000 = 255.255.255.248
/30 = 11111111.11111111.11111111.11111100 = 255.255.255.252
/31 = 11111111.11111111.11111111.11111110 = 255.255.255.254
/32 = 11111111.11111111.11111111.11111111 = 255.255.255.255
172.16.0.0/27 means: a subnet of the class B network 172.16.0.0 (default network mask = 255.255.0.0 or /16) network address = 172.16.0.0 host adresses: 172.16.0.1 - 172.16.0.30 broadcast adress = 172.16.0.31
Here it is explained by someone else: http://www.nongnu.org/lpi-manuals/lpi-102/html/ch05s02.html
[Edit] Thanks Gargoyle, you hit the nail right on the head [/Edit] [Edit] 192.168.1.* would be 192.168.1.0/24 [/Edit]
Edited by Witto (2007-12-02 04:58 PM)
|
Top
|
|
|
|
#183156 - 2007-12-02 05:33 PM
Re: Installing packages via GPO Startup script.
[Re: Shawn]
|
Arend_
MM club member
Registered: 2005-01-17
Posts: 1894
Loc: Hilversum, The Netherlands
|
Why not stick the GPO to the OU the computer is in and be done with it, no scripting neccesary
|
Top
|
|
|
|
#183174 - 2007-12-02 09:55 PM
Re: Installing packages via GPO Startup script.
[Re: Witto]
|
Shawn
Administrator
Registered: 1999-08-13
Posts: 8611
|
I have a gut-feeling this concept will work. Every workstation will run the script, and logic would be something like:
if (this workstation is in scope for package A)
install package A
enndif
if (this workstation is in scope for package B)
install package B
endif
etc, etc
Its the determination of "in-scope" I need to work-out. Unfortunately that could be just about anything ... from a simple list of hostnames to some other more complex criteria (like using the IP address). Will probably just custom code these IF statements as opposed to "softening them up" in an INI file like you did (your way is more eloquent imho).
|
Top
|
|
|
|
#183175 - 2007-12-02 10:06 PM
Re: Installing packages via GPO Startup script.
[Re: Shawn]
|
Witto
MM club member
Registered: 2004-09-29
Posts: 1828
Loc: Belgium
|
If I understand what you mean, that is also in the script. The INI file contains a section per package. Create a GPO per section. In the Startup Script parameters, you refer to the section:\\domain-name\SysVol\domain-name\scripts\script.kix $INI="\\domain-name\SysVol\domain-name\scripts\script.ini" $Section="Package Name"
|
Top
|
|
|
|
#183179 - 2007-12-03 01:07 AM
Re: Installing packages via GPO Startup script.
[Re: NTDOC]
|
Shawn
Administrator
Registered: 1999-08-13
Posts: 8611
|
Lol. Nah - we're putting out UPHClean. Having big problems with locked registry on logoff - especially on our VMWARE sessions.
-Shawn
|
Top
|
|
|
|
#183183 - 2007-12-03 05:23 AM
Re: Installing packages via GPO Startup script.
[Re: Shawn]
|
NTDOC
Administrator
Registered: 2000-07-28
Posts: 11623
Loc: CA
|
Oh... we don't need to push it out as it's in all our Ghost images
Been using it for years in our images, since my Disney days.
Though I'm about 99% certain that some recent "Critical Update" from MS is causing a yellow exclamation in the Event Viewer about the registry hive of the current user not be released properly. Never used to see it till recently and MS updates are the only things that get added to most of these systems and users are not Admins.
Have not really researched much more as it still unloads quickly due to UPH but PITA that MS changed something that is now causing it to happen on systems that had clean logs for months.
|
Top
|
|
|
|
Moderator: Glenn Barnas, NTDOC, Arend_, Jochen, Radimus, Allen, ShaneEP, Ruud van Velsen, Mart
|
2 registered
(morganw, mole)
and 414 anonymous users online.
|
|
|