- Posts: 68
- Thank you received: 0
SMS running program trouble
18 years 2 months ago #16877
by asab
Replied by asab on topic Re: SMS running program trouble
hello there again,
didn't find the batch file in SMS_PKGD.
if you don't find it there, what do you do next?
thanks for the help.
didn't find the batch file in SMS_PKGD.
if you don't find it there, what do you do next?
thanks for the help.
18 years 2 months ago #16894
by TheBishop
Replied by TheBishop on topic Re: SMS running program trouble
If your SMS infrastructure has worked properly in the past then we can assume everything is set up correctly. That being the case, I think you need to redo this current package. The basic procedure is:
1) Put your installation script and supporting files somewhere on your SMS server. Note that the supporting files must be in the right folder structure and that the script must correctly call them. That is to say, the installation package must work if you run it manually. Just one mistake and all is in vain!
2) Create a package in SMS. Point it to the files considered above. Make sure the path you use is not specific to a machine - it needs to be something like \\server\share\package as SMS will need to access it network-wide, not C:\folder package or similar
3) Create a job in which only the distribution option is ticked (untick the client install) to copy the package to all distribution servers. Let this loose and check for success. You should now be able to find the package in SMS_PKGD on all your distribution servers
4) Create a job that runs the install on a few specified machines (set up a test group in SMS machine groups). Check that this runs okay and the package installs as expected
5) If all is well, create a job that installs the package everywhere you want and let it loose
The above approach is not the only way to do it, but it allows you to troubleshoot safely at various stages and lessens the risk of unleashing something onto all your clients that might earn you a one-way ticket to the Jobcentre :lol:
1) Put your installation script and supporting files somewhere on your SMS server. Note that the supporting files must be in the right folder structure and that the script must correctly call them. That is to say, the installation package must work if you run it manually. Just one mistake and all is in vain!
2) Create a package in SMS. Point it to the files considered above. Make sure the path you use is not specific to a machine - it needs to be something like \\server\share\package as SMS will need to access it network-wide, not C:\folder package or similar
3) Create a job in which only the distribution option is ticked (untick the client install) to copy the package to all distribution servers. Let this loose and check for success. You should now be able to find the package in SMS_PKGD on all your distribution servers
4) Create a job that runs the install on a few specified machines (set up a test group in SMS machine groups). Check that this runs okay and the package installs as expected
5) If all is well, create a job that installs the package everywhere you want and let it loose
The above approach is not the only way to do it, but it allows you to troubleshoot safely at various stages and lessens the risk of unleashing something onto all your clients that might earn you a one-way ticket to the Jobcentre :lol:
Time to create page: 0.114 seconds