schooltech06

Hello, I'm getting SCCM 2012 R2 setup and I'm having problems getting collections to incrementally update by themselves. I've discovered all the computer systems in the domain and created a collection with a query to select only workstations. After I push a client, the built-in "All Desktop an Server Clients" collection is updated within 5 minutes but my custom collection is not. I can leave it overnight and the custom collection doesn't update, until I click the Update Membership button. Then it instantly updates with the new clients. I have Incremental Updates enabled and set to update every 5 minutes and a full eval every 7 days. The log file during an incremental show it finding changes, but the it doesn't update the actual collection: PF: [Express Evaluator] starts to evaluate collection [SC100010] PF: Incrementally refreshing collection SC100010 Evaluating 3 incremental changes for collection SC100010. Results refreshed for collection SC100010, 0 entries changed. PF: [Express Evaluator] successfully evaluated collection [SC100010] and used 1.063 seconds Anyone have any thoughts on what I'm doing wrong? I could swear this worked fine on the SCCM 2012 system I setup last year... Thanks

I think I figured the problem. All our clients are 64-bit Windows 7. Apparently when SCCM runs a script, it uses a 32-bit command line. From what I can tell, I was calling Bcdedit and the 32-bit command line was redirecting it to C:\Windows\Syswow64 where there is no BCDEdit. I found this blog entry that talks about the issue http://madluka.wordpress.com/2012/09/24/configmgr-2012-64bit-file-system-redirection-bites-again/ I tried using his suggested code at the top of my batch file and the BCD file actually gets changed now. IF "%PROCESSOR_ARCHITEW6432%"=="" GOTO native %SystemRoot%\Sysnative\cmd.exe /c %0 %* Exit :native <your script starts here> It's still returning an exit code of 1 saying there was an error, but that could be because of the new code I added.

I did. If I run it as a normal non-admin user it fails. If I run it from an elevated command prompt, it works fine and makes the changes to the BCD file.

Hi everyone, I'm trying to push a simple batch file that will disable startup repair on windows 7. The batch file is only 2 lines but needs to run as an administrator: bcdedit /set {default} recoveryenabled No bcdedit /set {default} bootstatuspolicy ignoreallfailures I saved that as a .bat and created a package to deploy it to a collection. I set the command line option to be the name of the bat file, set it as a required package and set it to run as Administrator. When it runs on the client machine, the execmgr log shows it running and exiting with error code 1. No changes are made in bcdedit. If I copy the script to the local machine, run a command prompt as admin, and run the script, it works fine. It seems like it's a permissions issue on the account that SCCM uses to run the script. Are there certain SCCM accounts that should be local admins on the client computers? I have no issues when installing MSI's and EXE's using SCCM, but I can't figure this one out. Any pointers anyone can offer? Thanks