Jump to content


SRed

Established Members
  • Content Count

    41
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by SRed

  1. Hi guys, The Microsoft documentation on this is looking pretty sparse on these topics. Does anyone know if it is possible to provision conditional access for mail when InTune is integrated with ConfigMgr? If so, is the process different at all from setting up conditional access when doing Intune standalone? Also, it seems like the documentation is actually empty for configuring mail profiles using ConfigMgr!!!! Anyone have a good walkthrough on the topic? Thanks! Stephen
  2. Sounds like your SetupWindows and ConfigMan step is failing. This normally happens if something is off for your SCCM Install Package, I've had it happen when I had the incorrect path specified for patches, for instance. For some reason, it was circulating around that the path to patches should be: 'C:\_SMSTASKSEQUENCE\OSD\CAS00002\CLIENT\HOTFIX\KB2905002\CLIENT\I386\CONFIGMGR2012AC-R2-KB2905002-I386.MSP'. The path should be Packages, not OSD. Check the ccmsetup for ccmsetup.log and client.msi.log and you'll find the answer.
  3. Hello all, For a client, we have a number of small offices with a local IT resource in charge of the systems there, something thing 45 offices. We've created query based collections to limit the local IT to seeing only their computers in the console, and this is working fine. However, we also have a large number of Software Distribution collections, and we want local IT to be able to place the users in those collections to deploy software. How do I allow the local IT user to do so, without having to manually add Application Deployment Manager to each one of these collections, f
  4. Sorry to resurrect this thread! These are great steps Niall, but I'm not sure about Content Distribution. At what point do I push the content out to DPs for distribution to end clients? Does the "Automatically download content when packages are assigned to branch distribution points" handle this for me? Note: I don't have any BDPs just standard DPs in my environment. Thanks!
  5. I also fixed my other issue! In case anyone else is plagued by those annoying errors in ConfigMan, here is how to fix them. Find the error (in this case SMS_Coll_Evaluator) Look for the time stamp and the relevant bad collection name Check the colleval.log file on the primary. Look for the time indicated, then search for the offending collection name(CCP00A37, in this example) Notice that the step before the highlighted step is refreshing results for collection CCP00ADD. If we look at the SQL Statement below it, we will see a direct rule stating If "the OS is Win NT 6.1 a
  6. Actually, I've figured out how to delete bad computer associations and fix invalid certificates. Open management Studio Browse down to the table you need to change. Choose Open Table Get the GUID from the relevant event in the SCCM console Create a select Statement to test what the query will affect Modify above command to make a delete command DELETE FROM ClientKeyData WHERE SMSID = 'GUID:1C53E10F-8BED-44AB-8671-B4A749156F4A' Now, can someone tell me where I would find collections in SQL? I've got two that appear to be bad and I'd like to remove them fro
  7. Hi guys, At two of my clients, I've recently noticed my primary sites going red due to an SCCM event 620. This event correlates to a SQL Message 208 or 547, the text of which is " Microsoft SQL Server reported SQL message 547, severity 16: [23000][547][Microsoft][ODBC SQL Server Driver] The DELETE statement conflicted with the REFERENCE constraint "StateMigrationAssociation_MachineIdGroupXRef_FK". The conflict occurred in database "SCCM_US1", table "dbo.StateMigrationAssociation" The other error is : " Microsoft SQL Server reported SQL message 208, severity 16: [42S02][208][M
  8. Hi all, I'm at a client site where a monthly reboot is forced on certain workstations using SCCM. This package only contains a single program with a command line of 'shutdown -r', and it used on certain kiosk machines. I'm trying to empty out the 'All Active Package Distributions' report by the clients request. Unfortunately, this package is listed as 'Waiting to Install Package' on every distribution point. Have you all ever run into this? This is an all SCCM 2007 R2 environment on Server R2. Thanks,
  9. Hi all, During a deployment for a client, a mission critical workstation began to hang on "Deploying Updates". I'm wondering, is there any command I can run in a command prompt to force the Task Sequence to proceed to the next step? The reason this is an issue is that this workstation is using XP to Windows 7 with Hard Link Migration and our update step is much before the USMT Restore step. We're concerned with having to do a USMT hard-link restore from Windows 7, and also with all of the automation steps we'll miss out on if we have to do the rest of the migration manually.
  10. Hi guys, On deployment with a client, we've had a strange issue in which USMT will create numerous desktop shortcut icons on a migrated users desktop. Lets say if a PC hasd six user profiles on the machine, after migration the primary user on the workstation will now has seven copies! One for themself and it appears one for each migrated user! This is a Windows XP to Windows 7 migration using SCCM 2007 Integrated with MDT 2010 (I know, I know, need to upgrade). Any thoughts? A note, this is an environment with redirected profiles, including desktop folder, to a us
  11. Turns out that I actually had the script in the %DeployRoot% folder, and hadn't updated the WinPE image. On top of that, I also had a number of errors in my script, which is why I never saw any messages about the script running in my BDD and SMSTS logs. I've since fixed it, thank you anyway!
  12. Thanks for the reply. I placed both the script and the exe in the \\Mdt\DeploymentShare$\Scripts folder. This is the value of %ScriptRoot%, right?
  13. Hi guys, For a recent client, I've had to automate the removal of Alternate Data Stream information from files, as this was causing ImageX to crash while taking a .WIM backup of critical systems. We would see the file name listed in the BDD and ZtiBackup.logs with an error code 2 next to the file name. Massive trial and error lead me to the discovery that some files with Zone Identifier or other types of Meta data can cause imageX to fail. I discovered Mark Russinovich's excellent Streams.exe tool, which is made to read and destroy ADS info, and it perfectly solves this problem. When
  14. Hi all, I'm engineering an MDT2012 Task Sequence to migrate users from XP to 7. First I use Hard link migration, then I reboot to capture a .WIM backup using ZTIBackup data in WinPE, followd by the Windows installation. In Win7 to Win7, I seem to never have any issue, deployments complete without any problems. However in Xp to 7, using PC's with actual user data, I am experiencing a very high, nearly 85% failure on the ImageX step. I get errors in ZTIBackup.log and in BDD.log that the system cannot find the file specified. Fearing disk errors, I've added a Disk Cleanup pass
  15. Good find Niall. As it turns out, the Component Status of the site server is that the SMS_Policy_Provider is in Critical condition, stating that The site server signing certificate has expired 0 day(s) ago. Please replace/renew the certificate. The Policies at this Site will be re-signed by the Site Server using the new signing certificate. So, it looks like my Site Server certificate expired, which coincidentally caused this whole issue. Unless somehow installing this patch caused my certificate to expire. *puts on aluminum foil hat*
  16. Okay, just tried the PXE OSD process with a brand new, out of box laptop, to make sure there weren't any random errors from redeploying systems. It ALSO is failing the same way. Able to boot into WinPE, but then failing with "There are no task sequences advertised to this computer". So...something is happening here. My certificates look good. The computers are getting into WinPE, so that tells me Windows Deployment Services works. I made a new advertisement and tried that, so I think my advertisement works. I think the only real option now is that somehow the Task Sequence
  17. Ok, I've tried this, and now with a different laptop and a new advertisement of the same task sequence, I'm STILL getting "There are no Task Sequences available to [for] this computer. Please verify..." in my SMSTS.log. This is becoming scary. I found another post about OSD Task Sequences fail nearly immediately, and thought this might be related to an expired SCCM PXE Certificate, as found in this post (http://social.techne...5-0df3dec1c5ef/, and this post http://www.windows-n...ficate-expired/); however, checking the records, my certificate looks to be fine! Any suggestions?
  18. I've check my smspxe.log file and this is what I see for this computer. MAC=D8:D3:85:9A:BC:3F SMBIOS GUID=2E061ADC-3758-11DF-95DA-90006701A06D > Device found in the database. MacCount=1 GuidCount=1 smspxe 8/10/2012 8:17:00 AM 7968 (0x1F20) [192.168.215.030:67] Recv From:[000.000.000.000:68] Len:548 1a61230 smspxe 8/10/2012 8:17:02 AM 7504 (0x1D50) Ignoring req from [000.000.000.000:68] Dest Server:[204.004.245.010] smspxe 8/10/2012 8:17:02 AM 7504 (0x1D50) [192.168.215.030:4011] Recv From:[192.168.215.133:68] Len:548 12de2f0 smspxe 8/10/2012 8:17:02 AM 7504 (0x1D50) [192.168.215.030:4
  19. Niall, you're on the ball! Thank you for the quick reply, this won't be the first time you've pulled my fat out of the fire! Here is my SMSTS.log. Maybe it is coincidental that the Task Sequence is failing now, I'm not sure why this update would seem to break things. Also, here is a screen cap of the computer in SCCM. It definitely has an advertisement. This is one of the ones that I deleted from SCCM in a panic, and recreated, just to be sure. I've check to make sure there are no duplicate entries either. e: somehow posted a screen cap of the wrong computer record. smsts.log
  20. Hey guys, Today I re-enabled my Software Updates step in my OSD Task Sequence, which had been disabled previously. I then noted that my new systems were hanging at Installing Updates with "Downloading 1 of 147, 0% out of 100". I did some googling and found KB2509007, which is supposed to resolved this. So I installed this on my site server and went to test it out, after updating my task sequence with the appropriate new command under Setup Windows and ConfigMgr. However, now when I try to do my tried-and-true OSD deployment on these systems (after clearing PXE records, and eve
  21. Thanks for the quick reply Peter! We have SCCM R3 installed. How can I create App-V packages for it? Do you have any good information on enabling the App-V role? Nevermind, I just found all of your posts under the SCCM\AppV area.
  22. Hi guys, We're looking at spinning up App-v in our environment to handle some finnicky Office 32-bit addins that we use for some line of business applications in my organization. My question : we've already got a working SCCM 2007 infrastructure, with SQL server and everything in place; is it possible to install App-V on a separate VM or even the same VM with SCCM and store the database for App-V in a separate instance on the same SQL server? Is this a bad idea? Also, how big of a deal is it to setup App-v? I'm intrigued by the idea and would love to experiment with some ad
  23. Hey guys, I'm posting this here from my post on TechNet. I'm getting frustrated because I feel that I must be doing this wrong somehow. Basically my issue is that I feel that I must be doing unnecessary work somewhere here, and want to make it all easier on me. We're about to begin migrating user's from an old pc to a new one, though the new one may also have been present in SCCM. The new PC will be renamed along the process. Here is my current procedure: In SCCM, import new computer record, and create computer association with Source PC Place Source PC in USMT Capture collect
  24. Figured it out, I didn't add a copy of my MigPst.Xml file to my USMT 32-bit folder. I'd only placed it in USMT for x64, and the command line was failing. The key to solving this was in finding the Scanstate.log file in C:\Windows\System32\CCM\Logs, which contained the following
×
×
  • Create New...