hofsteda

We looked into Casper, but the mandatory $4k in training was a deal breaker. We're using deploystudio for the mac side with a sysprep'd winclone image on the drive. We have an ard task that partitions the drive and extracts the winclone image. We might just keep this and do some automation of the ccm client install. Once the client is on the collection handles the ads for the bootcamp specific ads. We do some devcon to kill the airport cards in windows.

Sorry about the delay. We just went through a break week and I was busy breaking things. sccm runs under the system account, but I doubt this is related to your issue. You used to be able to do an at /interactive cmd.exe from an admin command prompt to get a cmd shell running under the system context. That would help isolate if it was a permission issue. Compare the hklm\software\microsoft\windows\currentversion\uninstall (f3 search for itunes) installsource value for the path to the cached msi for both the sccm install and admin prompt install. Verify the user has access to this location for the sccm version. If there is any install on first use, or install on first run by each user the lack of access to the msi on the sccm verison will cause these errors. I didn't roll 10.2.2.14 out. I'm going from 10.2.2.12 to 10.3.1.55.

Has anyone had any luck with running an MDT OSD image task sequence onto a boot camp partition? We've been using NetRestore, but would really like to avoid having to maintain separate windows images for the Macs. The last time we worked with this a year ago, we weren't able to come up with a boot media that would work. We also tried installing windows and the sccm client and running a refresh. That appeared to work except the install files were getting lost during the wipe phase.

check the web server logs on the dp point for errors from that client. I've seen the appconfig in IIS cause some strangeness like this. I would expect all installs to fail though, not just osd ones.

Just a FYI for the Itunes stuff. I just noticed with the latest updates the AppleMobileDeviceService is locking dll files for the update. The update completes, but I'm going to try a sc stop "Apple Mobile Device" prior to the install to avoid this.

That was bad phrasing on my part. With Itunes/quicktime and some other software it's a software distribution and install the new version for every update. I prefer to push updates through SCCM software updates, but I'm not willing to beat my head against the wall trying to get apple stuff packaged well enough for that to work. The BTNewerProduct broken logic with the MSI installs was bad enough. I'd love it if they would publish msp patches or even a msi that actually worked. The last few shockwave/flash cycles, I've imported the standard msi's into software updates with relatively good results. Acrobat patches install nicely through software updates. I did java that way for a update or two, but went back to an Software Ad with 1.6u24.

The stale duplicates I deal with most are due to the way we deal with machines having hardware upgraded. We run AD discovery. When a new replacement machine is deployed, it is given a temporary name. When the machine goes out, it is renamed on top of the old machine in ad. The old ccm record is kept alive due to the ad discovery. The new record doesn't get discovered from ad once it is renamed since the dn is already tied to the old record. They show up as you describe with the assigned set to yes.

In native mode I believe the sccm certificate is available from AD using the machines credentials, which are reset when the machine is re-added to the domain, and this is used to confirm the machine's identity. I've seen the scripts that allow automerging but manually merging hasn't been an issue as it hasn't happened that often.

Under site properties, Advanced tab, we have conflict management set to manual. This prevents new records from being created for the same hardware and instead creates an entry under conflicting records which we merge. This retains the history of the old object. Here's a good link discussing the issue including why Microsoft doesn't automerge Elmunjos Blog: Managing conflicting records and duplicate GUIDs in Configuration Manager 2007.

Check the log location for the quicktime log. What are the errors listed? What is the error code thrown in the TS? If pushing in an OSD ts, make sure the log path exists or remove the logging, /l*v filepath/filename. That one bit me as I usually log in the pwd. If you have the log path set for PWD and you run the osd packages off the DP instead of downloading you will get a failure due to file perms. We create %systemdrive%/scripts early in the TS on all our builds, so I now tend to log there for packages that get pushed in an OSD. For the Dell Bios, Since I haven't posted enough to answer PMs yet, I've used the Dell Client Configuration Utility to create executables with the bios passwords embedded. If you use passwords and try to do bios updates either through the dell System Center Update Publisher cab, from the update executable directly, the updates will fail unless you remove the passwords first. This is also all done outside the OSD on our machines as Software distribution ads on the model collections. James Avery - Deploying Dell BIOS Updates with and without Bitlocker through ConfigMgr (SCCM) has directions on creating a TS for removing the bios password, bitlocker, doing the update, and resetting afterwards.

Most of what I use came from appdeploy.com. Some of the transforms I use have came forward several versions so some of the edits may no longer be necessary. 10 is better than 9. I used to curse apple soundly back then. Start an itunes install and dig the msi's out of the temp folder. I have transforms created with orca for bonjour.msi, AppleMobileDeviceSupport.msi, quicktime.msi, itunes.msi. Quicktime is installed/updated with msiexec.exe /qn i appleapplicationsupport.msi /L*v %systemdrive%\scripts\appleappsupport.log Reboot=ReallySuppress msiexec.exe /qn /i quicktime.msi /t quicktime.mst /L*v %systemdrive%\scripts\quicktime.log Reboot=ReallySuppress Itunes has those two lines plus similiar lines for applemobiledevicesupport.msi, bonjour.msi, itunes.msi. The scripts folder is a logging folder we have on every machine. You can drop the whole /L*v section. We use it on most msi installs to trace install failures. Transforms: applemobiledevicesupport.msi -->LaunchCondition table->Drop Not BNEWERPRODUCTINSTALLED Had issues with false positives at one point. -->Property Table->IAcceptLicense Value=Yes Bounjour.msi -->LaunchCondition drop NOT BNEWWERPRODUCTINSTALLED -->Property table IAcceptLicense value=Yes -->Shortcut Table-> AboutBonjour -> Don't remember why I dropped this one. Quicktime.msi -->LaunchCondition table drop NOT BNEWERPRODUCTINSTALLED -->Property table SCHEDULE_ASUW value=0 -->Registry Table Drop Quicktime Task (key=SOFTWARE\Microsoft\Windows\currentversion\run) -->shortcut tables dropped QuicktimePlayer_desktop, QuicktimeUninstaller, QuicktimeReadme (apple really pissed me off I guess to get rid of the readme) Itunes.msi -->Component Table ItunesDesktopShortcuts ->Condition DESKTOP_SHORTCUTS="0" -->CustomAction table drop QuicktimeInstallFailed -->Property table IAcceptLicense Value=Yes SCHEDULE_ASUW value=0 -->Shortcut table Drop AboutItunes Looks like I missed the ituneshelper run key in itunes.msi. Quicktime is a fully supported application. Itunes we just patch to keep it up to date and to curtail the number of times we give out admin rights. So far no one has complained about it not working.

Pretty much what riffleman said. If you have a need to group machines, create a collection structure for it. I try to have all but optional software query based. Advertisements ->All Machines ----> allmachines phase3 ----------->FacStaffph3 ----------->Classroomsph3 ------------>allmachinesphase2 ------------------>facstaffph2 ------------------>classroomsph2 ------------------>allmachinesphase1 ----------------------->facstaffph1 ----------------------->classroomsph1 ------------------------>testgroup ---------------------------->facstafftest ---------------------------->classroomtest -->Staff Only (laid out and linked to same collections above just facstaff) -->Labs/classrooms (laid out and linked to same collections above but just labs) Grouped By Model ---->Optiplex270s ---->Optiplex280s etc. Specific Apps-> ----> Itunes ---------->Itunes test/install ----------->Itunes remove etc The ads that go on all machines or all of a class of machine are walked up from testing to phase3. Software updates use these trees also. Machines are auto-assigned to the appropriate phase2 collection by query unless assigned to one of the other collections. Model collections are for bios settings and updates Specific apps is used to target optional software root collections of an app are query based using add\remove. New installs are manually be assigned to install collection. On upgrade roll out, we add queries to the install collection for machines with software and member of phase1,2,3. The queries for Java are a little trickier as we have a collection of machines not to update. Each lab has a collection-Lab specific software is assigned there. I like the idea of the scheduled one as we've been toying with the idea of re-imaging some of our machines on a weekly schedule.