SCCM 2007 standalone USB is prompting for media

Hello. I have been creating standalone media on USB for a while. This week I needed to create new standalone media with an updated image and 3 new packages.
I modified the same TSs in SCCM 2007 I always use to create the standalone media on USB. The USB sticks are 16 gig and I diskpart like usual.
After creating the new standalone media on USB, I tested the sticks.
It deploys the image and drivers successfully but when it is attempting to install the packages (applications) I get a popup asking me to insert the media for the install.
I checked the USB stick and the packages are all there and I can launch the packages successfully.
I also advertised the TSs and can deploy via advertisement.
Any ideas? I have to get these done as soon as possible. WIll appreciate the help.
Charles

Did you find the source of the problem? I am running into the same issue but it appears to only occur on certain brands or models of USB stick.
Also, unplugging the stick, plugging it back in, and clicking OK on the media prompt allows the process to continue.
BWitz

Similar Messages

Using an External HD with USB 1.1 for Media (Movie files) storage?

Many thanks for your attention.
For a Media Storage (mostly movies) HD, I ordered a Maxtor OneTouch II with Firewire and the company mistakenly sent me one with USB 1.1 instead.
I remember reading that for Media Storage, only the Firwire connection will work (for Macs). Or that there are a lot of problems with USB.
Before sending this HD back to company, just checking to see if this is so.
Also (when I get the correct Drive), I've heard that in order to store a Movie File, (a movie on Final Cut Pro or iMovie, etc.), the External Hard Drive MUST be formatted as a "Mac Extended (Journaled)" Hard Drive.
Posting here for people's thoughts, opinions (hopefully not contradictory).
- Ross

Send it back.
Even USB 2.0 isn't good for media. Fast transfer rate, but not a sustained one.
USB 1 won't work AT ALL.
RETURN!
Shane
"There's no need to fear, UNDERDOG is here!"

SCCM 2007 R2 - configuration item compliance for a collection.

Hi All,
Can some one share the information of reports for configuration item compliance of for a collection in SCCM 2007 R2 using desired configuration management feature.
Rgs,

Yes, but no data shows up.
What does this mean? What troubleshooting have you done? When do you create the DCM?
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Standalone USB 3.0 "insert media #1 for the tasksequence...

Hi,
I have multiple USB 3.0 sticks with the standalone tasksequence (windows 7) on that stop installing.
I can boot i WinPE and the stick is recognized (since I imported the USB drivers in winPE 4.0). So I can start the installation.
However, after the "apply OS image" step and after the "apply driver packages" step the system reboots in the new Windows 7 env to continue the TS but the USB stick is no longer recognized and i'm asked to insert media #1 ...
I have to remove the stick, and put it a second later back in the same USB port, then it gets recognized again and the installation can continue. I tried to resolve the problem by importing the USB3.0 drivers straight into the windows7 OS before my initial
capture... Same problem.
The drivers are there, the stick is just not recognized during the reboot... it only gets recognized when i remove, re-enter it.
This is a problem for years now, but since our new laptops no longer have USB2 ports, it gets a big pain...
Anybody an idea how to solve this ?
Thanks a lot !
Jeroen

Hi,
I suggest you ask this question in Windows 7 forum, you could get better support from there.
http://social.technet.microsoft.com/Forums/en-US/home?category=w7itpro
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Lenovo X1 Carbon PXe boot errors with SCCM 2007

I know there are many posts on this and I've gone through them all, but I am still having issues PXe booting a X1. I have a USB ethernet dongle (the new type with the rounded edge). the part number is 0b67708. It's branded Lenovo but when I pxe it recognises it as ASIX AX88772b. So far so good. It picks up an IP from DHCP ok, recognises the hardware as x64 and then tries to download the \smsboot\boot.sdi file from the SCCM 2007 server. It waits for 20 seconds then falls over with the following:
Status: 0xc0000001 - Info: The boot selection failed because a required device is inaccessible.
Now, I have the the following drivers in the boot.wim file:
x86 -
1. Lenovo USB2.0 Ethernet Adapter 5.12.7.0
2. PCI bus
3. Intel ICHR/DO/DH SATA AHCI Controller
4. Intel USB 3.0 Root Hub
5. Intel USB 3.0 eXtensible Host Controller
x64 -
1. Lenovo USB 2.0 Ethernet Adapter 5.14.4.0
2. PCI Bus
3. Intel ICHR/DO/DH SATA AHCI Controller - 2821
4. Intel USB 3.0 Root Hub
5. Intel USB 3.0 eXtensible Host Controller
I have tried using the ASIX drivers, all previous driver version, adding in the mass storage drivers, adding in the USB 3.0 drivers, praying to the PXe gods but nothing works.
All other hardware works fine. Any suggestions greatly welcomed.
Cheers - Mark.

Make a USB recovery drive before reinstalling.Thats the only option with a preload. With a retail serial number, you can download an iso with the upgrade assistant.
Also, how much ram do you have. If yopu have more than 4GB, you will need 64 bit XP, or the performance will take a hit. I tried XP on my W530, but I had to change several settings in the BIOS/UEFI.
W530(2436-CTO): i7-3720QM, nVidia Quadro K2000M,16GB RAM, 500 GB hard drive, 128GB mSATA SSD, Ubuntu 14.04 Gnome, Centrino Ultimate-N 6300.
Yoga 3 Pro: Intel Core-M 5Y70, Intel HD 5300, 8GB RAM, 128GB eMMC, Windows 8.1, Broadcom Wireless 802.11ac.

Can I use SCCM 2007 to deploy SCCM 2012 Agent

I was reading the scenarios for deploying the SCCM 2012 agent here
http://technet.microsoft.com/en-us/library/gg682132.aspx
I have been planning to deploy the 2012 agent using an SCCM 2007 deployment package. I am not migrating any data/packages/collections/anything from SCCM 2007.
I am looking for a sane way to deploy 2000ish clients a day for 2 weeks and be done.
I figure they are all SCCM 2007 clients so lets deploy 2012 agent using SCCM 2007.
I read the following in the link above and it sounds like the way I want to go – use SCCM 2007 software distribution…
Upgrade installation by using application management
Upgrades clients to a newer version by using Configuration Manager application management. You can also use Configuration Manager 2007 software
distribution to upgrade clients to System Center 2012 Configuration Manager.
Then later in the same document there is this…
How to Upgrade Configuration Manager Clients by Using a Package and Program
You can use Configuration Manager to create and deploy a package and program that upgrades the client software for selected computers in your hierarchy. A package definition file
is supplied with Configuration Manager that populates the package properties with typically used values. You can customize the behavior of the client installation by specifying additional command line properties.
You cannot upgrade Configuration Manager 2007 clients to System Center 2012 Configuration Manager by using this method.
In this scenario, use automatic client upgrade, which automatically creates and deploys a package that contains the latest version of the client.
What???!?? There is no Automatic client upgrade feature in 2007 – so how does that even make sense? In one section, it says I can deploy the 2012 Agent using SCCM 2007 software distribution, and then later in the same document, it
says I can't. I am probably misunderstanding somthing.
Is it possible to make a package/program in SCCM 2007 that will make targeted clients upgrade to Agent 2012 and join the new SCCM 2012 Site?

I tested this (deploying 2012 agent using existing 2007 SCCM infrastructure) with a few test systems at my desk and it seems to work pretty smoothly. I made a package to deploy SCCM 2012 SP1 and added it to my SCCM 2007 Site. Then I deployed
the 2012 agent from 2007 and it worked great. If it works this well in production, I will be able to migrate all of my clients in less than a weeks time.
I have not published the 2012 site information in AD - and I don't plan to. We would have some overlapping site boundaries - and in 2012 it seems its unnecessary in a single site hierarchy. I AM planning to use boundaries to assign
DPs, but thankfully site and DP boundaries have been separated. It works great to just specify the site in everything and not worry about auto discovery. My clients don't move among sites since I only have one large site.
Sorry that I somehow posted this same question twice, and thanks for cleaning that up.
In my installation, I just called ccmsetup.exe with the following command line...
/mp:myMP.mydomain.com CCMLOGMAXHISTORY=5 CCMLOGMAXSIZE=1000000 SMSCACHEFLAGS=PERCENTDISKSPACE;NTFSONLY SMSCACHESIZE=10 SMSMP=myMP.mydomain.com SMSSITECODE=CCM
I am not sure that I need to specify the MP twice, but it is working to do so. I'm also not sure whether the log and cache flags will be honored since there are existing settings from SCCM2007 agent. I think that the 2012 install will not change
these settings upon installation, but it does not appear to hurt the process to include them just in case it does work.

Can you deploy an application sequenced with App-V v5 with SCCM 2007?

We are currently in the process of upgrading to SCCM 2012. We are also embarking on testing App-V v5. Can we deploy sequenced applications from App-V v5 using SCCM 2007? What limitations will exist with SCCM 2007? What release of
SCCM 2007 should we be at for App-V v5 sequenced applications to be deployed and/or streamed?

This KB article is now available: Supported Configuration Manager and Microsoft Application Virtualization scenarios
Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or click "Unmark as Answer" if a marked post does not actually
answer your question). This can be beneficial to other community members reading the thread.
This forum post is my own opinion and does not necessarily reflect the opinion or view of my employer, Microsoft, its employees, or other MVPs.
Twitter:
@stealthpuppy | Blog:
stealthpuppy.com |
The Definitive Guide to Delivering Microsoft Office with App-V

SCCM 2007 R3 / Offline USB Media

Has anyone come across a issue where they are having problems installation msi applications from a usb media deployment (created using 'Create Task Sequence Media')?
The task sequence runs fine, without any issues, if run from SCCM server/DP
If I create a external usb media, I can boot into Windows PE, it applies the wim and starts to install the software. The task eventually fails with 1612 error, unknown media..
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Looking for sourcelist for product {AC76BA86-7AD7-1033-7B44-AB0000000001}
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Adding {AC76BA86-7AD7-1033-7B44-AB0000000001}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Now checking product {AC76BA86-7AD7-1033-7B44-AB0000000001}
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Media is enabled for product.
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1402 2: UNKNOWN\Media 3: 2
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1402 2: UNKNOWN\Media 3: 2
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Attempting to use raw LastUsedSource value.
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Source with value name 'LastUsedSource' is blank
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1706 2: -2147483647 3: AcroRead.msi
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Processing net source list.
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1402 2: UNKNOWN\Net 3: 2
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1706 2: -2147483647 3: AcroRead.msi
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Processing media source list.
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1402 2: UNKNOWN\Media 3: 2
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1402 2: UNKNOWN\Media 3: 2
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1402 2: UNKNOWN\Media 3: 2
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1706 2: -2147483647 3: AcroRead.msi
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Processing URL source list.
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1706 2: -2147483647 3: AcroRead.msi
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1706 2: 3: AcroRead.msi
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Failed to resolve source
MSI (s) (D4:B4) [13:51:20:999]: MainEngineThread is returning 1612
Anyone with any ideas?
This seems to happen to all the packages installed from the usb media

The boot order is already set to boot from HD first
Running a normal PXE OSD build using the same task sequence works.. i only have issues when i used use a standalone media of the task sequence (i've tried both USB and DVD)
For some reason once the Win7 image is applied, the next step in the task sequence is to install applications..
The first application installation task eventually fails with 1612 error, unknown media..
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Looking for sourcelist for product {AC76BA86-7AD7-1033-7B44-AB0000000001}

SCCM 2007 - task sequence - prestaged media - self-signed certificates - error message 'Certificate has expired for this media'

Hi there
Quick scenario.
We have created a task sequence prestaged media .wim file (SCCM 2007, client OS is Windows XP).
Recently some of these swap-out machinses, on delivery and start up, have started showing this message:
'Certificate has expired for this media'.
This is because the self-signed certificate created during the prestaged media creation process has expired.
My question is: is it possible to mount the image using dism or imagex and then inject an updated sertificate?
Best regards
John

the disk that has the prestaged media applied must be the boot partition.
create a task sequence to stage the prestaged media. In this task run a format and partition step which configures both the system disk and the os disk, though make the os disk the active boot partition. Then apply the prestage wim.
On your deploy task, somewhere after the OS has applied create a group that runs only if the media is OEM (from memory _SMSTSMedia =
OEMMedia)
in this group run the command bcdboot C:\Windows /s F: /f ALL where f: is the drive letter assigned to the system disk, then run another step that removes the drive letter and reboots. The deploy task will now continue and you will be booting to the system
partition.
So I wanted to get back to working on this issue. I noticed that when I said it Worked that it was actually still booting from C drive instead of the reserved partition. For the past few days I have been trying to get the prestaged to work like
a network deploy but fail every time. I cannot get the prestaged to boot from any other partition other then the partition where windows was imaged too.
So where I am at today. When I do as suggest above the D drive (The reserved Boot volume) return on reboot. it will not stay hidden. also the OS is till booting from C and does not change to the D drive or no drive letter drive with the above
commands. I think there is some other command missing that tells it to boot from a new location that is not bcdboot.
Has anyone seen any guides for how to use prestaged and bitlocker enabled task sequence? I think that would help me figure out my current issues as with bitlocker you must have this other partition.

For Your Consideration: Ultimate Lync 2010 client install with SCCM 2007

While the subject of my post may be very presumptuous, I submit the following for your consideration to answer the often-asked question about how to deploy Lync 2010 client with SCCM.
Background:
I cannot understand why Microsoft made the Lync install so darned confusing, complex, and convoluted.
After our Lync 2010 FE server was up and running and all users migrated off our OCS server to the Lync environment, I spent about a month and a half trying to figure out how to:
1. Uninstall the OCS 2007 R2 client
2. Install all prerequisites for the Lync client
3. Install Lync on all user workstations silently.
While researching this, the simple answer I kept seeing given to this question was, "just use the .exe with the right switches according to the TechNet article here: http://technet.microsoft.com/en-us/library/gg425733.aspx". Well, my response is, I
tried that and while the program installed itself correctly pushed through SCCM, because I was doing it using an administrative account (i.e. the SYSTEM account) due to our users not having admin rights, when the install was done, Lync would automatically
start up, but in the SYSTEM context so that the user couldn't see it was running, they go to run it and it won't run for them. I was unable to find any switch or option to prevent the automatic launch. I suppose the simple solution to that would
be to have the user reboot, but that's unnecessarily disruptive and was contrary to the desire to make this a silent install.
The next simplest answer I saw was, "extract the MSI and use that with the right switches". Problem with that is that the MSI by itself doesn't remove the OCS client or install the prerequisites, and also either requires a registry change to even allow
the MSI to be used or a hacked MSI that bypasses the registry key check. I tried to put a package together to uninstall OCS, install the prereqs, and use a hacked MSI, but I never could get the MSI hacked properly. The other problem I ran into
was detecting if the OCS client was running in a predictable way so I could terminate it, properly uninstall it, and then do the rest of the installations. It was this problem that ultimately led me to the solution that I'm about to detail and that has
worked marvellously for us.
Solution:
As I said before, when I first looked at this problem, I started by building a typical software deployment package (Computer Management -> Software Distribution -> Packages) and then created the programs to do the install. My first attempt was
just with the .exe file provided as-is by Microsoft using the switches they document in the link above for IT-Managed Installation of Lync, and...well, the end result wasn't quite as desirable as hoped. So, my next attempt was to extract all the prerequisite
files and the Lync install MSI (both for x86 and x64), attempt to hack it to get around the "UseMSIForLyncInstallation" registry key, and make the command-lines to terminate OCS and uninstall it.
In the past when I had an install to do with SCCM that also required uninstalling an older version of a given application, I typically used the program-chaining technique. That's where you have, for example, 3 or more programs that run in a package
in a sequence and you have Program 3 be set to run after Program 2 does and then set Program 2 to run after Program 1 so you get the desired sequence of Programs 1-2-3 running in that order. So, I created programs to 1) kill Communicator.exe 2) uninstall
Communicator 2007 R2 by doing an "msiexec /uninstall {GUID}" 3) install Silverlight 4) install Visual C++ x86 5) optionally install Visual C++ x64, and then 6) install the Lync x86 or x64 client. That final step was always the point of failure because
I couldn't get the hacked MSI for the Lync Client install to work. I also realized that if Communicator wasn't running when the deployment started, that step would fail and cause the whole process to bail out with an error. That's one of the downsides
of program-chaining, if one step fails, SCCM completely bails on the deployment. This is what also led me to the key to my solution: TASK SEQUENCES.
I'm not sure how many people out there look in the "Operating System Deployment" area of SCCM 2007 where Task Sequences normally live, but I also wonder how many people realize that Task Sequences can be used for more than just Operating System deployments.
One of the biggest advantages of a task sequence is you can set a step to ignore an error condition, such as if you try to terminate a process that isn't running. Another advantage is that task sequences have some very good built-in conditionals that
you can apply to steps, for example, having the sequence skip a step if a certain application (or specific version of an application) is not installed on the machine. Both of those advantages factor highly into my solution.
OK, for those who already think this is "TL;DR", here's the step-by-step of how to do this:
First, you need to extract all the files from the LyncSetup.exe for your needed architectures. We have a mix of Windows XP and Windows 7 64-bit, so my solution here will take both possibilities into account. To extract the files, just start up
the .exe like you're going to install it, but then when the first dialog comes up, navigate to "%programfiles%\OCSetup" and copy everything there to a new location. The main files you need are: Silverlight.exe, vcredist.exe (the x64 LyncSetup.exe includes
both x86 and x64 Visual C++ runtimes, you need them both, just rename them to differentiate), and Lync.msi (this also comes in an x86 and x64 flavor, so if you have a mix of architectures in your environment, get both and either put them into their own directories
or rename them to reflect the architecture).
For my setup, I extracted the files for the x86 and x64 clients and just dumped them each into directories named after the architectures.
Next, move these files into a directory to your SCCM file server, whatever it might be that you deploy from, in our case, it was just another volume on our central site server. Go to the SCCM console into Computer Management -> Software Distribution
-> Packages and then create a new package, call it something meaningful, and then point to the directory on your SCCM file server for the source files.
Now you need to create 3 to 5 programs inside the package:
1. Name: Silverlight
   Command Line: x86\Silverlight.exe /q     (remember, inside my main Lync install folder on my distribution point, I have an x86 directory for the files from the x86 installer and an x64 folder for the files from the x64 installer.
The fact is the Silverlight installer is the same in both, so you only need one of them.)
   On the Environment tab: Program can run whether or not a user is logged in, runs with administrative rights, Runs with UNC name
   On the Advanced tab: Suppress program notifications
   All other options leave default.
2. Name: Visual C++ x86
    Command Line: x86\vcredist_x86.exe /q
   On the Requirements tab: Click the radio button next to "This program can run only on specified client platforms:" and then check off the desired x86 clients.
   Environment and Advanced tabs: same as Silverlight
   (If you have only x64 clients in your environment, change all x86 references to x64. If you have a mixed environment, create another program identical to this one, replacing references to x86 with x64.)
3. Name: Lync x86
    Command Line: msiexec /qn /i x86\Lync.msi OCSETUPDIR="C:\Program Files\Microsoft Lync" (The OCSETUPDIR fixes the issue with the Lync client wanting to "reinstall" itself every time it starts up)
    Requirements, Environment, and Advanced tabs: Same as with Visual C++ and Silverlight
    (Same deal as above if you have all x64 clients or a mix, either change this program to reflect or make a second program if necessary)
Now you need to make the Task Sequence. Go to Computer Management -> Operating System Deployment -> Task Sequences. Under the Actions pane, click New -> Task Sequence. In the Create a New Task Sequence dialog, choose "create a
new custom task sequence", Next, enter a meaningful name for the task sequence like "Install Microsoft Lync", Next, Next, Close.
The task sequence will have up to 12 steps in it. I'll break the steps down into 3 phases, the prereqs phase, uninstall OCS phase, and then Lync install phase.
Prereqs Phase:
These are the easiest of the steps to do. Highlight the task sequence and then in the Actions pane, click Edit.
1. Click Add -> General -> Install Software. Name: "Install Microsoft Silverlight". Select "Install a single application", browse to the Lync package created earlier and then select the Silverlight program.
2. Add -> General -> Install Software. Name: "Install Microsoft Visual C++ 2008 x86". Install Single Application, browse to the Lync package, select the Visual C++ x86 package.
As before, if you're an all-x64 environment, replace the x86 references with x64. If you have a mixed environment, repeat step 2, replacing x86 with x64.
3. Add -> General -> Run Command Line. Name: "Enable Lync Installation". This step gets around the UseMSIForLyncInstallation registry requirement. The Lync client MSI simply looks for the presence of this key when it runs, so
we'll inject it into the registry now and it doesn't require a reboot or anything. It just has to be there before the client MSI starts.
Command Line: reg add "hklm\Software\Policies\Microsoft\Communicator" /v UseMSIForLyncInstallation /t REG_DWORD /d 1 /f
Uninstall OCS Phase:
This part consists of up to 6 Run Command Line steps. (Add -> General -> Run Command Line)
4. Name: "Terminate Communicator". Command Line: "taskkill /f /im communicator.exe". On the Options page, check the box next to "Continue on error". This will terminate the Communicator process if it's running, and if it's not, it'll
ignore the error.
5. Name: "Terminate Outlook". Command Line: "taskkill /f /im OUTLOOK.exe". Check the "Continue on error" on the Options page here too. Communicator 2007 hooks into Outlook, so if you don't kill Outlook, it might prompt for a reboot
because components are in use.
(NOTE: If necessary, you could also add another step that terminates Internet Explorer because Communicator does hook into IE and without killing IE, it might require a restart after uninstalling Communicator in the next steps. I didn't run into
this in my environment, though. Just repeat step 5, but replace OUTLOOK.EXE with IEXPLORE.EXE)
6. Name: "Uninstall Microsoft Office Communicator 2007". Command Line: "msiexec.exe /qn /uninstall {E5BA0430-919F-46DD-B656-0796F8A5ADFF} /norestart" On the Options page: Add Condition -> Installed Software -> Browse to the
Office Communicator 2007 non-R2 MSI -> select "Match this specific product (Product Code and Upgrade Code)".
7. Name: "Uninstall Microsoft Office Communicator 2007 R2". Command Line: "msiexec.exe /qn /uninstall {0D1CBBB9-F4A8-45B6-95E7-202BA61D7AF4} /norestart". On the Options page: Add Condition -> Installed Software ->
Browse to the Office Communicator 2007 R2 MSI -> select "Match any version of this product (Upgrade Code Only)".
SIDEBAR
OK, I need to stop here and explain steps 6 and 7 in more detail because it was a gotcha that bit me after I'd already started deploying Lync with this task sequence. I found out after I'd been deploying for a while that a tech in one of our remote
offices was reinstalling machines and putting the Communicator 2007 non-R2 client on instead of the R2 client, and my task sequence was expecting R2, mostly because I thought we didn't have any non-R2 clients out there. So, at first I just had our Help
Desk people do those installs manually, but later on decided to add support for this possibility into my task sequence. Now, when you normally uninstall something with msiexec, you would use the Product Code GUID in the command, as you see in steps 6
and 7. All applications have a Product Code that's unique to a specific version of an application, but applications also have an Upgrade Code GUID that is unique for an application but common across versions. This is part of how Windows knows that
Application X version 1.2 is an upgrade to Application X version 1.1, i.e. Application X would have a common Upgrade Code, but the Product Code would differ between versions 1.1 and 1.2.
The complication comes in that Communicator 2007 and Communicator 2007 R2 have a common Upgrade Code, but different Product Codes and the "MSIEXEC /uninstall" command uses the Product Code, not the Upgrade Code. This means that if I didn't have step
6 to catch the non-R2 clients, step 7 would be fine for the R2 clients, but fail on non-R2 clients because the Product Code in the MSIEXEC command would be wrong. Luckily, we only had one version of the non-R2 client to deal with versus 4 or 5 versions
of the R2 client. So, I put the command to remove Communicator 2007 non-R2 first and checked for that specific product and version on the machine. If it was present, it uninstalled it and then skipped over the R2 step. If non-R2 was not present,
it skipped that step and instead uninstalled any version of the R2 client. It's important that steps 6 and 7 are in the order they are because if you swap them, then you'd have the same outcome as if step 6 wasn't there. What if neither is on the
machine? Well the collection this was targeted to included only machines with any version of Communicator 2007 installed, so this was not a problem. It was assumed that the machines had some version of Communicator on them.
8. Name: "Uninstall Conferencing Add-In for Outlook". Command Line: "msiexec.exe /qn /uninstall {730000A1-6206-4597-966F-953827FC40F7} /norestart". Check the "Continue on error" on the Options Page and then Add Condition ->
Installed Software -> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
9. Name: "Uninstall Live Meeting 2007". Command Line: "msiexec.exe /qn /uninstall {69CEBEF8-52AA-4436-A3C9-684AF57B0307} /norestart". Check the "Continue on error" on the Options Page and then Add Condition -> Installed Software
-> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
Install Lync phase:
Now, finally the main event, and it's pretty simple:
10. Click Add -> General -> Install Software. Name: "Install Microsoft Lync 2010 x86". Select "Install a single application", browse to the Lync package created earlier and then select the "Lync x86" program. As before, if you
only have x64 in your environment, replace the x86 with x64, or if you have a mixed environment, copy this step, replacing x86 references with x64.
And the task sequence is done! The final thing you need to do now is highlight the task, click Advertise in the Actions pane, and deploy it to a collection like you would with any other software distribution advertisement. Go get a beer!
Some final notes to keep in mind:
1. You can't make a task sequence totally silent...easily. Users will get balloon notifications that an application is available to install. The notifications cannot be suppressed through the GUI. I've found scripts that supposedly
hack the advertisement to make it be silent, but neither of them worked for me. It was OK, though because in the end we wanted users, especially laptop users, to be able to pick a convenient time to do the upgrade. The task sequence will appear
in the "Add/Remove Programs" or "Programs and Features" Control Panel. You can still do mandatory assignments to force the install to happen, you just can't make it totally silent. On the plus side, the user shouldn't have to reboot at any point
during or after the install!
2. In the advertisement setup, you can optionally show the task sequence progress. I've configured the individual installs in this process to be silent, however, I did show the user the task sequence progress. This means instead of seeing
5 or 6 Installer windows pop up and go away, the user will have a single progress bar with the name of the step that is executing.
3. One step that I didn't consider when I actually did this was starting the Lync client as the user when the install was complete. The user either had to start the client manually or just let it start on its own at the next logon. However,
while I was writing this, I realized that I could possibly start the client after installing by making another Program in the Lync Package with a command line that was along the lines of "%programfiles%\Microsoft Lync\communicator.exe" and then in the Environment
tab, set it to "Run with user's rights" "only when a user is logged on".
4. My first revision of this task sequence has the Prereqs phase happening after the OCS uninstall phase, but I kept running into problems where the Silverlight installer would throw some bizarre error that it couldn't open a window or something wacky
and it would fail. Problem was, I couldn't re-run the task sequence because now it would fail because OCS had been uninstalled, so that's why the Prereqs happen first. It ran much more reliably this way.
5. For some reason that baffles me, when I'd check the logs on the Site Server to monitor the deployment, I'd frequently see situations where the task sequence would start on a given machine, complete successfully, almost immediately start again, and
then fail. I'm not sure what is causing that, but I suspect either users are going to Add/Remove Programs and double-clicking the Add button to start the install instead of just single-clicking it, or the notification that they have software to install
doesn't go away immediately or Lync doesn't start up right after the install, so they think the first time it didn't take and try it a second time.
I hope this helps some of you SCCM and Lync admins out there!

On Step 8 I found multiple product codes for the Conferencing Add-In for Outlook. Here's a list of the ones I found in the machines on my network:
{987CAEDE-EB67-4D5A-B0C0-AE0640A17B5F}
{2BB9B2F5-79E7-4220-B903-22E849100547}
{13BEAC7C-69C1-4A9E-89A3-D5F311DE2B69}
{C5586971-E3A9-432A-93B7-D1D0EF076764}
I'm sure there's others one, just be mindful that this add-in will have numerous product codes.

How to prompt for OU during OSD Task with SCCM 2012 R2?

How to prompt for OU during OSD Task with SCCM 2012 R2?

Hi,
Here is an example on how to do it using a Variable prompt in Configuration Manager, It works the same way in SCCM 2007,
http://www.the-d-spot.org/wordpress/2013/04/01/dynamically-join-computer-to-ad-ou-during-osd-with-sccm/
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Can I set up multiple usb hard drives- one for time machine and a second for media? Can one also print wirelessly with an old HP C6280 printer?

Can I set up multiple usb hard drives- one for time machine and a second for media?
Can one also print wirelessly with an old HP C6280 printer?

Can I set up multiple usb hard drives- one for time machine and a second for media?
Yes.
Can one also print wirelessly with an old HP C6280 printer?
Possibly by using an Airport Express, but depends on what type of port connection the printer requires.

SCCM 2012 R2: Build and Capture - Windows 8.1 prompting for network

I have upgraded my SCCM 2012 SP1 (CU2) to SCCM 2012 R2 and I am attempting to Build and Capture Windows 8.1 Enterprise. Everything is perfect except for the OS prompting for a network selection during the process, if I click "next" on that screen
the Capture finishes without incident. The same is true of the Deploy as well...
Is this a bug from my upgrade?
Portland Public Schools / Systems Administrator II

Hi LillonelC
Can you point out how and where to do this?
When capturing with MDT 2013 on VMware I do not see this, naturaly, since the "machine" only has one network adapter.
But when deploying to a Laptop I get the wireless Setup screen...
On beforehand Thank You!
With kind regards
We aren't using MDT but what we did was create a package called Windows 8.1 - Compnents. In it placed a file named "32Bit-Unattend.xml" and 1 named "64Bit-Unattend.xml".
During the capture in the "Apply Operating System Image" I put a check in the box "Use an unattended or Sysprep answer file for a custom installation". The package was Windows 8.1 - Compnents the File name was "32Bit-Unattend.xml".
I did the same for 64-bit and used the 64-bit version.
Here is content of the 32-bit file:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideLocalAccountScreen>true</HideLocalAccountScreen>
</OOBE>
</component>
</settings>
<cpi:offlineImage cpi:source="wim://SERVERNAME/e$/osimages/win_8.1_x86/sources/install.wim#Windows 8.1 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
Here is the content of the 64-bit file:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideLocalAccountScreen>true</HideLocalAccountScreen>
</OOBE>
</component>
</settings>
<cpi:offlineImage cpi:source="wim://SERVERNAME/e$/osimages/win_8.1_x64/sources/install.wim#Windows 8.1 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
If that doesn't help I can try to clarify it a bit further.
PS You won't need to do this for the deploy, only the capture.
Portland Public Schools / Systems Administrator II

Exchange 2007 to 2013 Migration issues. Prompt for credentials, Public Folders inaccessible, Apps not working

Exchange 2013 Migration issues
I have three issues and decided to list them here. Please pick and choose to assist. Thanks in advance.
Environment:
Mixed 2007 SP3 R12 and 2013 CU3. 2007 Environment was webmail.domain.com. I installed new Exchange 2013 (1 CAS, 1 Mailbox) according to:
http://technet.microsoft.com/en-us/library/ff805032(v=exchg.150).aspx. Exchange 2007 is now legacy.domain.com and Exchange 2013 CAS is webmail.domain.com.
Machine 1: Windows 8.1, not domain joined, using Outlook Anywhere external. Outlook 2013
Machine 2: Windows 7, domain joined, using Outlook Anywhere internal. Outlook 2010 SP2
I have migrated 1 user so far to Exchange 2013. This user was a Domain Admin. I have removed that membership. I checked the box to inherit permissions of the security of the object and reset the AdminCount attribute in ADSIedit to 0 and verified this replicated
to all domain controllers. ( I originally thought this to be the issue with it prompting for the password. )
Here is a Get-OutlookAnywhere cmdlet...
ServerName                         : EXCHANGE2007SVR
SSLOffloading                      : False
ExternalHostname                   : legacy.domain.com
InternalHostname                   :
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Basic
IISAuthenticationMethods           : {Basic}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : False
MetabasePath                       : IIS://EXCHANGE2007SVR.domain.local/W3SVC/1/ROOT/Rpc
Path                               : C:\WINDOWS\System32\RpcProxy
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 8.3 (Build 83.6)
Server                             :
EXCHANGE2007SVR
AdminDisplayName                   :
ExchangeVersion                    : 0.1 (8.0.535.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCHANGE2007SVR,CN=Servers,CN=Exchange
                                     Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                     Groups,CN=DOMAIN,CN=Microsoft
                                     Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=local
Identity                           : EXCHANGE2007SVR\Rpc (Default Web Site)
Guid                               : 4901bb14-ab81-4ded-8bab-d5ee57785416
ObjectCategory                     : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 12/31/2013 4:08:04 PM
WhenCreated                        : 7/18/2008 10:56:46 AM
WhenChangedUTC                     : 12/31/2013 9:08:04 PM
WhenCreatedUTC                     : 7/18/2008 2:56:46 PM
OrganizationId                     :
OriginatingServer                  : DC1.domain.local
IsValid                            : True
ObjectState                        : Changed
ServerName                         :
EXCHANGE2013SVR
SSLOffloading                      : True
ExternalHostname                   : webmail.domain.com
InternalHostname                   : webmail.domain.com
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       : IIS://EXCHANGE2013SVR.domain.local/W3SVC/1/ROOT/Rpc
Path                               : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 15.0 (Build 775.38)
Server                             : EXCHANGE2013SVR
AdminDisplayName                   :
ExchangeVersion                    : 0.20 (15.0.0.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCHANGE2013SVR,CN=Servers,CN=Exchange
                                     Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                     Groups,CN=DOMAIN,CN=Microsoft
                                     Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=local
Identity                           : EXCHANGE2013SVR\Rpc (Default Web Site)
Guid                               : d983a4b1-6921-4a7f-af37-51de4a61b003
ObjectCategory                     : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 1/7/2014 11:29:05 AM
WhenCreated                        : 12/31/2013 1:17:42 PM
WhenChangedUTC                     : 1/7/2014 4:29:05 PM
WhenCreatedUTC                     : 12/31/2013 6:17:42 PM
OrganizationId                     :
OriginatingServer                  : DC1.domain.local
IsValid                            : True
ObjectState                        : Changed
ISSUE 1
Issue: On Machine 1 (reference above) Windows Security prompt that says "Connecting to
[email protected]". Almost always prompts when Outlook is first opened. Afterwards (if it goes away) seemingly random on when it asks for it. I put in the credentials (absolutely correct) and it fails and prompts again.
I always check the box for it to save the password. To get rid of it, I click the Cancel button at which Outlook reports "NEED PASSWORD", but still acts fine sending and receiving emails. Eventually the "NEED PASSWORD" sometimes changes
to say "CONNECTED", but it works regardless.
No issues on Machine 2 so I don't know where the problem might be as there are a lot of variables in play here.
ISSUE 2
Migrated user is unable to open Public folders from Exchange 2007.
Cannot expan the folder. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance. (/o=...).
This error occurs on Machine 1, Machine 2 and from OWA, same error each time.
ISSUE 3
Apps. Installed by default are 4 apps (Bing Maps, Suggested Meetings, Unsubscribe, Action Items). I have made sure the apps are enabled in OWA and they show up in mail items on both Machine 1 (Outlook 2013) and OWA. They do not show up in Machine 2 (Outlook
2010). I'm assuming that isn't supported.
In OWA, when I go to the installed apps listing it shows all of the apps but has a broken link on the image describing the app.
When I click the app in either Outlook 2013 or in OWA, I get "APP ERROR, Sorry we can't load the app. Please make sure you have network and/or internet connectivity. Click "Retry" once you're back online.
Current workaround is just disabling them through OWA.

Hello,
In order to avoid confusion, we troubleshoot a issue per thread usually.
For your first isue, I agree with Ed's suggestion to check if your certificate name is correct.
Besides, I recommend you change ExternalClientAuthenticationMethod from Basic authentication to Negotiate authentication to check the result.
For the second issue and third issue, please create a new post.
If you have any feedback on our support, please click here
Cara Chen
TechNet Community Support

Outlook 2013 Constantly Prompting For Credentials - Exchange 2007 - Small Business Server 2008

Hello, I am having a problem using Windows Small Business Server 2008 and Exchange 2007 with Outlook 2013. The issue is that a credentials box appears in Outlook 2013 when using there exchange account whilst connected to the domain. The box will randomly
prompt for user credentials, once the user credentials are entered it will either pop back up again and if you enter the details in again it will continue to pop up for around 4 or 5 times before accepting the credentials. It will then pop back up within 15
minutes and do the same thing, if you click "Cancel" on the box it will also go away and remain connected to exchange however a popup in the bottom right will appear asking for a password even though you can send / receive from the mailbox.
I have looked into this issue for hours and hours and still can not find a resolution, I have tried re-installing Office 2013 and re-creating the Outlook Profile as-well as as the Windows 7 Profile. I have checked through all the SSL certificates in IIS
and everything appear to be correct.
Is this a common issue? Is there anything I can do to further diagnose or fix this issue without having to try to re-install both the server and machine?

Hi James_wilson,
Any update?
Just additional, would you please let me know whether have installed all updates for Outlook 2013? If hasn’t, please install and then monitor the result.
Please also check if you enable
Always prompt for logon credentials setting in Outlook 2013.
If you enable this setting, please uncheck and check if this issue still persists. Meanwhile, please remove the old credential in
Credential Manager, then add again. Then monitor the result
By the way, please run the Exchange BPA on the SBS 2008 server and check if can find some issue.
Hope this helps.
Best regards,
Justin Gu

SCCM 2007 standalone USB is prompting for media

Similar Messages

Maybe you are looking for