<div>
Within the CIW for the administrative install (screen 12 I believe) have you specified the additional network servers that users can install from? &nbsp;Did you use path and not unc?
</div>


Within the CIW for the administrative install (screen 12 I believe) have you specified the additional network servers that users can install from?  Did you use path and not unc?

<div>
<div class="content wysiwyg-content">
I am having trouble setting up automated office 2000 installs at CHILD DOMAIN level. The automated install works okay at PARENT DOMAIN level for any computer accounts, but the same policy within the child domain fails to work!<br />
I have ensured the policy is being accessed by adding a sample script at computer level and this runs okay. Any ideas - it's driving me mad!!!
</div>
</div>


I am having trouble setting up automated office 2000 installs at CHILD DOMAIN level. The automated install works okay at PARENT DOMAIN level for any computer accounts, but the same policy within the child domain fails to work!
I have ensured the policy is being accessed by adding a sample script at computer level and this runs okay. Any ideas - it's driving me mad!!!

Group policy and remote installation of office2k

Windows 2000 is an operating system for use on both client and server computers. It is the successor to Windows NT 4.0, and is the last version of Microsoft Windows to display the "Windows NT" designation. Four editions of Windows 2000 were released (Professional, Server, Advanced Server, and Datacenter Server) that shared a core set of features, including many system utilities such as the Microsoft Management Console. All versions of the operating system support NTFS 3.0, Encrypting File System, as well as basic and dynamic disk storage. The Windows 2000 Server family includes support for Active Directory services, Distributed File System and fault-redundant storage volumes.