Agree with VBScab, lack of information provided results in lack responses to your post.
Anyways, SCCM allows vbscript deployments, so you might want to review the questions below and then recheck your deployment settings.
- Does the Vbscript function outwith SCCM?- Is your deployment a Package or Application?- Is it downloading the content to client ccmcache?- If not caching, have you made the content available by distributing content to DP's?- Within SCCM console, Monitoring, confirm distribution of Content Status for deployment has been successful?- Within SCCM console, Monitoring, what is the deployment status messages indicating? - If an Application, is the detection method correct, check the AppDiscovery.log &AppEnforce.log?- If a package does the command line have wscript/cscript included?- Are there any unique deployment requirement set that have not been met?- Are there any deployment pre-requisites not met?- Are there any unique user experience been set, eg only run when no user is logged on and a user is logged on?
If you dont have much experience of creating Packages/Applications, check out the following links -
https://technet.microsoft.com/en-gb/library/gg682112.aspx ( creating packages)
https://technet.microsoft.com/en-us/library/gg682159.aspx (creating applications)
Sign up today to participate,
stay informed, earn points and establish a reputation for yourself!