installing apps through active directory and group policy editor

[kev]

This is probably a common question, but I searched few search engines,
but I couldn't find any good information about it. I am a UNIX admin,
but these days, few companies are cutting the budget, so I gained the duty
of maintaining the Active Directory. My question might be very simple to
some of you. How would I convert setup.exe or plain no setup applications
to msi, so I can install it on the client machines through the Active
Directory and Policy Manager? This is so easy in Linux using crontab and
package managers. This seems very difficult in Windows. Is it also,
possible to use batch files in the combination with msi to install the
applications in the background while users are working? How would I also
install Windows Updates through the Active Directory, so all these
machines don't have to constantly contact Microsoft?

Thank you so much ahead of time.

 

[Myweb (M.Weber)]

Hello Kev,

Search for WinInstall LE on the internet or you can find it on a Windows
2000 server setup disc under Valueadd\3rdparty\mgmt\winstle
It is a small tool to create .msi packages.

Best regards

Myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

 

[kev]

Hello Kev,

Search for WinInstall LE on the internet or you can find it on a Windows
2000 server setup disc under Valueadd\3rdparty\mgmt\winstle
It is a small tool to create .msi packages.

I following the instruction on various forums.
1. I divided OU based on the policy level.
2. Apply the policy on a seperate OU.
3. I launched the policy editor inside that OU.
4. I went to software installation and browsed to "shared folder" that
contained the msi file. It is set to install the app. From the
workstation, I made sure the share can be accessed.
5. msi application is set to assigned.
6. when i login from other computer that is on the same OU that I
assigned, nothing happens. I checked the start group and went to
ADD/REMOVE section, and I don't see the app.
7. I also tested with other MSI files.
8. The client machine has been rebooted.

What am I doing wrong?

 

[kev]

never mind. i found the solution after pulling so much of my hairs out.
the dns was pointed to our unix dns server instead of dns server on the
active directory.