Jump to content


lucastee

Established Members
  • Posts

    8
  • Joined

  • Last visited

lucastee's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I might be blind. This can be achieved by setting the 'Rerun behaviour' to 'Always rerun program' on the device collection deployment. This option can be found under the scheduling tab in the deployment properties window or during the deployment wizard.
  2. Hi All, Is there a way to force a task sequence to rerun even if it had run successfully before on the PC? My situation is as follows: PC1 has Windows 7 installed through the SCCM task sequence. PC1 has issues, and requires its HD wiped and given a fresh build. Essentially, I'd like to be able to add PCs to a collection that forces those PCs to rerun the task sequence, despite it's previous successes/failures. PC1 does not rebuild in this instance as it already has the task sequence as 'installed' in the Software Center. Maybe I'm overlooking something obvious here, but if someone has done this before, a bit of help would be appreciated.
  3. I would suggest only adding the network interface drivers to the boot image. There is no real harm in adding more drivers, but the larger the boot file, the longer the deployment. If you're not too converned about adding a few extra minutes to the deployment time, then it shouldn't matter. However, deploying to 1000+ PCs, adding 3 minutes to each - you've added 50 hours of build time across the organisation. We have captured and deployed Windows 7 64-bit on both VM and physical hardware. The VMs are running VMWare.
  4. Thanks Peter33, I ended up getting this working after quite a bit of fiddling around. I was able to create a Status Filter Rule that simply ran my script whenever the return code matched the action. e.g 11143 is returned by the SMS Agent whenever a task sequence is complete. Add the action to 'Run program field' and I was good to go. Thanks for the help.
  5. Hi. Thanks for the reply. I was using the %msgsys variable because technet lists it as a status filter rule variable. (http://technet.micro...y/bb693758.aspx) It allows me to pass properties of the status message to the program it runs, or in this case, my powershell script. Ideally, I would like to have the script run as a status filter rule, instead of in a package, as it would allow me to run the same script no matter which task sequence runs. i.e I can pass the PC name and task sequence name to the script and have it report back to me. This eliminates overheads such as adding the script to each new task sequence. Admittedly, there won't be all that many, but I'd still like to do it this - if possible. Since posting, I have tried running the script with the switch -executionpolicy unrestricted, to no avail. Would setting it to bypass do any more? Thanks for all the help. Luke
  6. Hi All, I've been having some issues executing powershell scripts using the status filter rules. I am able to run VB scripts without issue, but powershell scripts do not seem to execute. I have a VBscript that runs under the same conditions which executes without issue. The PS script is a basic script to send an email to the SCCM administrators upon successful completion of a task sequence. It will work perfectly when run manually, under both administrator and system accounts context. Powershell Execution Policy is set to unrestricted. The command line for the script is 'powershell -file \\SCCM\d$\packages\scripts\complete.ps1 %msgsys' I have also tried directly pointing to D:\Packages\...etc. Any ideas?
  7. Hi all, Probably just a quick one but I cannot for the life of me find if this report exists or I am able to create it using SQL Report Builder. Essentially, I'd like to create a report that allows me to enter a device name and it will return the list of collections that it belongs to. e.g Entered: Device Name: PC1 Returned: Collections: Windows 7 PCs, Power-Saving Excluded. I'd like to be able to run this in the event that a PC needs to be moved. Looking through each device collection until I find each record is not ideal as I will have as many as 50 collections to look through. Any advice/suggestions would be appreciated.
  8. Hey there, Long time lurker, first time poster. I seem to be having issues with the PXE deployment aspect of SCCM 2012 RTM. I have deployed both boot images (x64 and x86). They are also listed as successful in the summary field. The network access account is clearly defined, and has domain access. I have tried adding a premade .WIM image created using ImageX, as well as creating a Operating System Images job using the source files from a Win7 ISO. Our clients get their IP from DHCP, and PXE is enabled on the SCCM server. No matter what I do, our clients will not boot into PXE. They get the error 'No boot file name recieved'. I have even tried defining the PXE server on the DHCP server using options 66 and 77. Note: The PXE server (sccm) and DHCP servers are different servers. We did have an AltirisPXE server running on the same domain, but it has been deactivated for SCCM testing. From the %installdir%\Logs\distmgr.log file, the only error I see when I distribute the packages is the following (taken directly from the log) ExpandPXEImage: C0100004, 1184 SMS_DISTRIBUTION_MANAGER 18/05/2012 10:36:44 AM 1540 (0x0604) Expanding C:\SCCMContentLib\FileLib\E4AD\E4AD46A6C40964E4C07C8D7499C4FEE2DD90BAEE0DC0071A7C7293EAE3B6211C from package C0100004 SMS_DISTRIBUTION_MANAGER 18/05/2012 10:36:44 AM 1540 (0x0604) Finding Wimgapi.Dll SMS_DISTRIBUTION_MANAGER 18/05/2012 10:36:44 AM 1540 (0x0604) Found WAIK upgrade code SMS_DISTRIBUTION_MANAGER WIMApplyImage failed for C:\SCCMContentLib\FileLib\E4AD\E4AD46A6C40964E4C07C8D7499C4FEE2DD90BAEE0DC0071A7C7293EAE3B6211C to C:\RemoteInstall\SMSTempBootFiles\C0100004 SMS_DISTRIBUTION_MANAGER ExtractPXEImage failed; 0x80070522 SMS_DISTRIBUTION_MANAGER Apparently this has to do with UAC being enabled, or that the user that is trying to access the folder requires elevated privledges to process the command. However, as a temporary measure, I have given the USERS group full access to the folders, source and destination. Oddly enough, I am able to deploy software without problems. Which I would have thought would need the same access in order to deploy. Any help would be greatly appreciated. I'm racking my brain over this. Regards, Luke
×
×
  • Create New...