D
Dave Shaw [MVP]
Software restriction is available only with Active Directory under Windows
Server 2003.
-ds
Server 2003.
-ds
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
R
Rick Gouin
Software restriction policies are available in both Windows 2000 and
2003 domains.
Regards,
Rick Gouin, MCSE
2003 domains.
Regards,
Rick Gouin, MCSE
R
rUAn
or it can be used in W2K3 domain.
Thanks ®ads,
Eric Eyecles
Thanks ®ads,
Eric Eyecles
C
Chriss3 [MVP]
Software Restriction Policies will be available as soon as the first Windows
Server 2003 Domain Controller are deployed within the particular active
directory domain. At the client side you have to run at least Windows XP.
--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services
No email replies please - reply in the newsgroup
Server 2003 Domain Controller are deployed within the particular active
directory domain. At the client side you have to run at least Windows XP.
--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services
No email replies please - reply in the newsgroup
R
Rick Gouin
I am currently using software restriction policies in a Windows 2000
domain against XP clients. I have no 2003 domain controllers anywhere
in the forest, and I never have.
After installing the latest GPMC and adm file updates to an XP client
that I manage my domain from, I was able to create and deploy software
restriction policies within my 2000 domain that are working perfectly
against my Windows XP clients.
Before you say I'm full of beans, try it. It works.
domain against XP clients. I have no 2003 domain controllers anywhere
in the forest, and I never have.
After installing the latest GPMC and adm file updates to an XP client
that I manage my domain from, I was able to create and deploy software
restriction policies within my 2000 domain that are working perfectly
against my Windows XP clients.
Before you say I'm full of beans, try it. It works.
C
Chriss3 [MVP]
Interesting, I didn't below the Software Restriction Module was within an
..adm file.
--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services
No email replies please - reply in the newsgroup
..adm file.
--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services
No email replies please - reply in the newsgroup
R
Rick Gouin
I'm not sure that it actually resides in an adm file
When I go onto any of my Win2k DC's (which don't have the GPMC or
anything installed on them) I can't manage the software restriction
policies. However from my desktop, I can, and they work. I don't know
whether that functionality was added due to the GPMC update, the SP2
adm file updates, 2k3 admin tools, or what.
Pretty cool, huh?
When I go onto any of my Win2k DC's (which don't have the GPMC or
anything installed on them) I can't manage the software restriction
policies. However from my desktop, I can, and they work. I don't know
whether that functionality was added due to the GPMC update, the SP2
adm file updates, 2k3 admin tools, or what.
Pretty cool, huh?
R
Rick Gouin
Definitely needs to be XP clients within an AD.
R
rUAn
Is this point absolute that the clients must be XP pro deployed within AD
environment.
Is it correct?
Thanks for your reply.
Regards,
Eric Eyecles
environment.
Is it correct?
Thanks for your reply.
Regards,
Eric Eyecles
C
Chriss3 [MVP]
Yes that is for sure.
--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services
No email replies please - reply in the newsgroup
--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services
No email replies please - reply in the newsgroup