Jump to content


Mike S

Established Members
  • Content Count

    37
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Mike S

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I finally got it working correctly. I re-installed all of the components used and it started "working" again. I am noticing that not all applications work correctly, even though they are fully functional through the Software Library. I'll have to figure that one out later. Thanks again Peter. Next time I am in Holland, I will have to buy you a drink.
  2. The only thing I could identify is the 2 401 codes (see below). Nothing is highlighted in yellow or red other than what is shown in the previous post. The damn thing just quit working...how strange. Here are the log entries for the powershell script: The execution scope for running the powershell script is specified not to verify the signature of the scripts. This is unsafe and potentially risk running malicious scripts. RunPowerShellScript 6/6/2014 12:55:12 PM 1324 (0x052C) Sending warning status message RunPowerShellScript 6/6/2014 12:55:12 PM 1324 (0x052C) Setting URL = http:/
  3. I rolled back to the working configuration I had a couple of days ago. Now, I am finding that this no longer works. I deleted everything and started over from scratch, hoping that my tinkering with things was what caused the problem. Everything is correct as far as I can tell, and the TS executes correctly up until the "Install Applications" sequence. The only error generated points towards the base variable not having the specified basename of "APPId". I double checked the script and it is there. I have not changed anything for the application. I am at a loss since the log file tell
  4. Since I have about 50 AD groups to configure, your script was a welcome relief. We are hoping to have a single OSD TS that will install applications based on user collections created using these AD memberships. Each user collection will have approximately 7 or 8 applications deployed to them. I have got to talk my boss into sending me to a powershell class.
  5. I am running into a rather interesting issue. When I add a new deployment to the user collection, the process fails. Additionally, when I add a second user collection to the container, the process also fails. The log looks good until the following error appears: No Env variable with specified basename APPId and suffix '01' is found. No applications installed. The sequence then aborts with an 80004004 code. The second deployment is configured exactly like the first one (except for the application, of course). Once I remove the deployment and the second user collection, the
  6. After testing this a couple of times, I decided to attempt using a collection based on a security group instead of individual users assigned to the group. The user set during the OSD deployment was a member of the security group assigned to the user collection. When I executed the OSD, it failed as soon as the get/install applications TS started. Can the automated process you developed be implemented with security groups, or will I need to ensure that each user be added to the correct application collection? My guess is that since the affinity is looking for a specific user to belong to
  7. I have fixed the above "problem". It seems that I forgot to check the little box in the application properties under the "General Information" tab that allows the application to be installed from the Install Application task sequence action without being deployed. I tested everything again and it worked like a charm (after about 40 attempts). I have got to learn more about powershell. Quick question, is there a limit to the number of applications that can be installed using this method? I know that if a manual list is used, only 8 applications can be installed per step. Wondering i
  8. You were correct, once I added the domain computers to the read-only analyst role, things ran smoother. However, the TS failed during the Install Applications TS. Do I need to ensure that the box is ticked under Deployment settings to enable "Pre-deploy software to the user's primary device"? Here is a snippet from the logfile: Retrieving Policy Assignments: InstallApplication 6/3/2014 3:39:11 PM 1548 (0x060C) assignmentList.size() > 0, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\dautils.cpp,452) InstallApplication 6/3/2014 3:39:11 PM 1548 (0
  9. Almost there. The TS "Install Applications" started to run this time. Unfortunately, it failed. I think it is due to incorrect permissions... Get-WmiObject : Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESS RunPowerShellScript 6/3/2014 9:00:08 AM 1908 (0x0774) DENIED)) RunPowerShellScript 6/3/2014 9:00:08 AM 1908 (0x0774) At C:\_SMSTaskSequence\Packages\DOR0008C\GetTargetedApplications_v0_9.ps1:21 ch RunPowerShellScript 6/2/2014 2:44:19 PM 2188 (0x088C) ar:34 RunPowerShellScript 6/2/2014 2:44:19 PM 2188 (0x088C) + $PrimaryUser = (Get-WmiObject <<<< -Compu
  10. I see clearer now. Scripting is not my strong suit. So my parameters should look like this: param ( [string]$ResourceName, [string]$SiteCode="DOR", [string]$SiteServer="SCCM2012DOR", [string]$Container="Applications" ) The $ResourceName is defined in the TS step "GetApplications"...correct?
  11. Found the SMSTS.log... The lines indented and in bold font are the errors that appeared. [ OSDRunPSScript.exe ] RunPowerShellScript 6/2/2014 11:36:34 AM 1920 (0x0780) Running powershell script: 'GetTargetedApplications_v0_9.ps1'(PkgID: DOR0008C) with execution policy: 'Bypass' RunPowerShellScript 6/2/2014 11:36:34 AM 1920 (0x0780) The execution scope for running the powershell script is specified not to verify the signature of the scripts. This is unsafe and potentially risk running malicious scripts. RunPowerShellScript 6/2/2014 11:36:34 AM 1920 (0x0780) Sending warning status message Run
  12. I have created a folder in User Collections called Applications. This sub-folder will contain all of the user collections for applications. For the container variable in the script, I used Applications as the variable. Is this sufficient, or do I need to define a specific path that directs the script to this container? It appears that there is more to this. The TS just failed with the error code 0x00000001. I am trying to find the logs now to see what went wrong.
  13. Does anyone have some sort of tutorial on how to do this? I have not figured out why I cannot get this to work. After 2 weeks of futility, I am ready to give up on this.
  14. hmmm, something went wrong. I am going to chalk the failure up to not knowing anything about powershell and how to use scripts in a TS. I am hoping that I can figure this out. Again, any advice i can get is greatly appreciated. I am running SCCM 2012 on a 2008 R2 server with a local instance of SQL 2012. When the OSD TS loads via boot media, I am prompted to enter in a primary user for the machine being loaded. This is accomplished using the SMSTSUdaUsers variable that I have pre-defined in the boot image. This part works. The deployment works fine until the powershell script
  15. Got it. Since I plan on implementing this script for all devices, can I use %_SMSTSMachineName% as the ResourceName?
×
×
  • Create New...