Jump to content


willisj318

Established Members
  • Content Count

    103
  • Joined

  • Last visited

  • Days Won

    4

willisj318 last won the day on May 14 2015

willisj318 had the most liked content!

Community Reputation

7 Neutral

About willisj318

  • Rank
    Advanced Member

Recent Profile Visitors

825 profile views
  1. Validation fixed the first issue. Is your issue still happening? It sounds a little different, sounds like the policy for the deletion of the deployment may not have been created successfully.
  2. Make sure you have a solid backup of any DBs even if the DB test runs OK. If they are VMs take a snapshot prior to upgrading.
  3. In SCCM remove it from the software update group(s) which are being deployed that it is a member of.
  4. Sounded like that to me too. No I will post there though thanks!
  5. Digging deeper. If they initiate the deployment from the collection, they can deploy OK, if they initiate the deployment from the TS itself, then they have the issue.
  6. We have upgraded SCCM from R2 to R2 w/ SP1 and CU1, we have not done CU2 yet, although I don't see fixes for these two issues listed in there. Issue 1. Anyone that is not a full admin (maybe more accurately, anyone set up with custom security) cannot deploy a task sequence with a required purpose. If they set the purpose as available, they can deploy it fine. This was working fine prior to the upgrade. What happens is when they hit the NEXT button on the deployment settings screen, it pauses a moment like it is processing, then refreshes to the same screen. Issue 2. Software inventory processing on the primary sites takes 30 seconds up to 1:30 to process a file single file, resulting in a backlog. Typically its around a minute per file. Again working fine prior to the upgrade. These are all delta as far as I can tell. Any help is appreciated!
  7. Does the machine show up under DEVICES in the SCCM Console, and state that it has the client and that the client is the correct version?
  8. I agree with Garth, what is the business need there? What are you trying to accomplish? But ultimately you should be able to do this with a scope and role. Create a scope and role, assign the query permissions as applicable. You would probably want a couple of Roles and scopes, one role for read and one for write, one scope for read and then an individual scope for each group. Give the pre canned queries access to the read scope. Then assign the group to the write scope. That should allow them to create queries and edit them. With this set up, other groups will only be able to read the queries created by the group if the group goes into their created query and assigns the read scope. I would have to mess around with it, but just go in and start trying some things and see if you can get it to work for you.
  9. Can you screenshot your deployment user experience tab for us. Under Device Restart Behavior, you want Servers NOT checked if you want them to reboot. Otherwise the reboot will be suppressed for those machines.
  10. I may have fixed the first issue, I have the validation set to run tonight. I will update accordingly.
  11. Try formatting the surface drive with a partition. Then boot to USB again. We have seen issues exactly as you explain them and this worked for us.
  12. Hi all, We are having two issues, similar, in a way, but I do not think related. One is that we have a DP trying to verify the content of a package that no longer exists. Failed to validate package "PackageID" on distribution point "["Display=\\DP2\"]MSWNET:["SMS_SITE=NPS"]\\DP2\". The package may not be present or may be corrupt. Please redistribute it. We have two DPs and this only happens on DP#2 Second is that colleval tries to distribute a package that does not exist. CCEPSource::GetCollectionInfo:- Collection Not Found with CollectionID=545 CEP-ErrorCode=-2016280319 CEP-Failed to process Collection Extended Properties changes, Status = COLLECTION NOT FOUND FOREIGN KEY CONSTRAINTS, changes will be retried on next processing cycle. Sounds like something with the DB table to me. In monitoring, the component status for colleval has this error about 3 times a minute. Collection Evaluator failed to process Collection Settings changes. These changes will be retried on next processing cycle. Solution: Review the previous status messages and logs for further clarification about this problem. This is message ID 2548 There is no previous error with any information. Any help is appreciated!!!
  13. I don't think you need a SUP at the factory, a DP will do with the details provided.
  14. Variables are represented by %variable% So in your script you would reference the TS Variable you create that way. I can't help on the script itself sorry.
×
×
  • Create New...