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.

Similar Messages

  • SCCM 2012 R2 coexist with SCCM 2007 - DPs issue

    Hi all,
    I have a SCCM 2012 R2 which coexists with SCCM 2007 and I'm not interested in a migration, but my question concerning the use of DPs. Is it possible for 2012 R2 clients to use a 2007 DPs, i.e. are there settings for a sort of compatibility? I've looked among
    links, but most of them are related to migration.
    Please advise,
    Domenico

    No, you can only share a distribution point during a migration between a source and destination hierarchy (see also:
    http://technet.microsoft.com/en-us/library/gg712275.aspx). Without a migration that's not possible. 
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • After Upgraded to SQL 2012 Iam getting several Errors in SCCM 2007

    After I upgrade my sql 2008 to sql 2012, I am getting several errors in SCCM 2007.Please find the below screen short
    Configmgr reporting service point - Critical
    SMS-Collection-Evaluator -critical
    SmS-dstribution Manager -Critical
    SMS-SRS reporting point -critical
    SMS-Discovery Data manager -critical
    SMS-Status Manager -critical
    SMS policy Manager -critical
    How can I resolve this issue.

    I updated the path still I have the same problem...several error message found in SCCM server.please find the below one error message
    On 7/21/2013 10:51:16 AM, component SMS_DISCOVERY_DATA_MANAGER on computer DCD-SCCM reported:  SMS Discovery Data Manager failed to process the discovery data record (DDR) "", because it cannot update the data source.
    Possible cause: On a Primary site, it is probably a SQL Server problem.
    Solution:
    1. Review the immediately preceding status messages from this component about SQL Server errors.
    2. Verify that this computer can reach the SQL Server computer.
    3. Verify that SQL Server services are running.
    4. Verify that SMS can access the SMS site database.
    5. Verify that the SMS site database, transaction log, and tempdb are not full.
    6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console.
    If the problem persists, check the SQL Server error logs.
    Possible cause: On a secondary site, SMS Discovery Data Manager probably cannot write to a file on the site server, so check for low disk space on the site server.
    Solution: Make more space available on the site server.
    how can I resolve the issue??

  • 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

  • Inventory with sccm 2007

    Hello,
    i have to make inventory with SCCM 2007.My boss asked me to collect important information (from hardwares and softwares) for both .The problem is that he didn't specify me whcih informations to collect.He just told me to do it seems like  i'm
    the  the workstation infrastructure manager and asked myself which crucial informations i have to collect.For information,we have both laptops and desktops in our infrastructure.And we have two types of OS for our workstation:Windows XP and windows 7.
    I really need help to know which crucial information do i have to collect.
    Thank you in advance yor all your propositions.

    You can refer this link for inventory : http://technet.microsoft.com/en-us/library/bb693889.aspx
    Later you can decide on the type of inventory.
    Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to 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.

  • PXE boot issue with DHCP and SCCM server on different subnets

    I'm working with a client on the operating system deployment module of SCCM.
    Their network configuration currently has a single large subnet for client
    computers with a DHCP server on the same subnet. The SCCM subnet is
    configured on a seperate subnet with no DHCP server on the subnet. We want to
    configure client computers to be able to boot using the PXE client to deploy
    OS images to the machines but can not get PXE-boot to work correctly.
    Also, the client does not want to make changes to their network
    infrastructure routers or switches to remedy this problem. Are there settings
    on the DHCP or SCCM servers we can implement to make this work? If so, what
    needs to be installed or configured on each server. We currently already have
    WDS installed on the SCCM server and the SCCM server is configured as a PXE
    Service Point within SCCM. Both WDS and the PXE Service Point seem to be working fine.
    Any help would be appreciated.
    Thanks,
    Gary

    I am Brazilian,
    sorry for wrong english
    My DHCP is on linux,
    in my own structure VLANS
    The system center is on the network
    10.0.4.0/24
    The machines on the network 10.0.5.0/24
    The problem is that the machines that
    are not on the same network system center
    can not boot
      I tried configuring / etc/dhcp3/dhcpd.conf
    follows
    option vendor-class-identifier "PXEClient";
    option bootfile-name "\
    \ SMSBOOT \ \ x86 \
    \ wdsnbp.com";
    option tftp-server-name
    "10.0.4.101"; ---->
    IP server
    But it did not work, anyone know
    how to configure?

  • PXE Boot issues with Latitude E5450.

    Our SCCM 2012 is SP1 and it does not  support Windows 8.1.
    I had tried to capture the OS through network but there were issues connecting and smsts.log indicated share not reachable. Hence, I captured the OS in the D:\ of the machine.
    Now after creating TS and deploying the OSD machine boots to PXE and starts to download boot image files and instantly restarts to Windows. I have performed below steps..
    1. Got the network drivers and updated the boot image with the same
    2. Checked the BIOS settings and time is updated correctly
    3. Used an old boot image that was used to capture another model laptop with Windows 8.1 and still same issue.
    Getting the below errors in smsts.log
    uExitCode == 0, HRESULT=80004005 (e:\nts_sccm_release\sms\server\pxe\tspxe\tspxe.cpp,185)
    TSPxe 3/26/2015 6:29:17 PM
    792 (0x0318)
    Failed to download pxe variable file. Code(0x00000001)
    TSPxe 3/26/2015 6:29:17 PM
    792 (0x0318)
    PxeGetPxeData failed with 0x80004005 TSPxe
    3/26/2015 6:29:17 PM 792 (0x0318)
    HRESULT_FROM_WIN32(dwError), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1416)
    TSPxe 3/26/2015 6:29:17 PM
    792 (0x0318)
    TSMBootstrapUtil::PxeGetPxeData(&bPxeBooted, sVariablesFile, sPxePasswd), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2623)
    TSPxe 3/26/2015 6:29:17 PM
    792 (0x0318)
    oTSMediaWizardControl.Run( sMediaRoot, true, sTSLaunchMode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1078)
    TSPxe 3/26/2015 6:29:17 PM
    792 (0x0318)
    Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1183)
    TSPxe 3/26/2015 6:29:17 PM
    792 (0x0318)
    Exiting with return code 0x80004005 TSPxe
    3/26/2015 6:29:17 PM 792 (0x0318)
    Any advise would be helpful..

    Our issue with the Latitude E5450 ended up being due to a boot image that wasn't being properly updated and/or pointed to during the task sequence set up.  There also seemed to be some strangeness with the replication because the WIM file listed on
    the server file system was showing as, for example, boot.XXXX.XXXX.wim (double name).  As a result, when we would update the boot image with the correct NIC driver, the system was still pointing to, for example, boot.XXXX.wim.
    We ended up re-creating the boot image from scratch using our base boot.wim image and using the 19.2.0.0/12.12.50.4 driver version for the I218-LM NIC, found at the download link below.  If you recreate the boot image, don't forget to re-add all of the
    NIC drivers, redistribute the boot image, and change which boot image your Task Sequence will be pointing to.
    http://www (dot) dell (dot) com/support/article/us/en/19/SLN294178/EN

  • OSD: pxe boot fails with "failed to get infromation for MP:/"

    Hi,
    We face an issue on pxe boot. It boots into pxe then tries to apply network settings but then reboots.
    Ipconfig is ok, smsts.log says "failed to get information for MP:/oursccmserver.
    Troubleshooting:
    *PXE is working fine when client as well as sccm-server are in same subnet, it fails when in different subnets.
    *Firewall is fully opened, no connections blocked.
    *Ping to sccm-server works fine on dns
    Please advise.
    J.
    smsts.log:
    Missing root CA environment variable from variables file    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Support Unknown Machines: 0    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Custom hook from X:\\TSConfig.INI is     TSPxe    26/03/2014 16:37:11    288 (0x0120)
    No hook is found to be executed before downloading policy    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Authenticator from the environment is empty.    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Need to create Authenticator Info using PFX    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Initialized CStringStream object with string: {40AB3050-A926-4BA5-9D17-7423F93CBCD5};2014-03-27T00:37:11Z.    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Set media certificate in transport    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Set authenticator in transport    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    CLibSMSMessageWinHttpTransport::Send: URL: oursccmserver.ourcompany.com:80  GET /SMS_MP/.sms_aut?MPKEYINFORMATIONMEDIA    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    [TSMESSAGING] AsyncCallback(): -----------------------------------------------------------------    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    [TSMESSAGING] AsyncCallback(): WINHTTP_CALLBACK_STATUS_SECURE_FAILURE Encountered    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    [TSMESSAGING]                : dwStatusInformationLength is 4
        TSPxe    26/03/2014 16:37:11    288 (0x0120)
    [TSMESSAGING]                : *lpvStatusInformation is 0x8
        TSPxe    26/03/2014 16:37:11    288 (0x0120)
    [TSMESSAGING]            : WINHTTP_CALLBACK_STATUS_FLAG_INVALID_CA is set
        TSPxe    26/03/2014 16:37:11    288 (0x0120)
    [TSMESSAGING] AsyncCallback(): -----------------------------------------------------------------    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    WinHttpReceiveResponse (hRequest, NULL), HRESULT=80072f8f (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,8927)    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    failed to receive response with winhttp; 80072f8f    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    m_pHttpTransport->Send (0, 0, pServerReply, nReplySize), HRESULT=80072f8f (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,5159)    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    MPKeyInformation.RequestMPKeyInformationForMedia(szTrustedRootKey), HRESULT=80072f8f (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,9410)    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Failed to get information for MP: http://oursccmserver.ourcompany.com. 80072f8f.    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Jan Hoedt

    Hi,
    Have you check Mpcontrol.log on the MP server and Smspxe.log?
    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.

  • PXE boot issues with Windows Deployment Services

    I am trying to move from FOG to WDS after running in to serious UEFI issues with FOG.Right now I'm stuck with machines PXE booting to WDS server.I keep getting the message ProxyDHCP service didn't reply to request on port 4011.WDS and DHCP are on different servers. There are plenty of IP addresses available, and they are on the same subnet. I did originally configure DHCP option 60, but deleted that option after troubleshooting. I have configured Windows Firewall to allow inbound and outbound connections on UDP ports 67-69 and 4011 on both DHCP server and WDS server. I have also tried just using IP address in DHCP option 66. As for option 67, I don't even know the right bootfile name to use at this point, figured I'd tackle that if I ever get past this error message.I have tried restarting the WDS service several times, as well as the...
    This topic first appeared in the Spiceworks Community

    After working with many companies in their Office 365 Change Management and End User Adoption strategies, we’ve found that companies who make it fun have very high success rates. So what can you to make it fun?Host an Office 365 Showcase.We’ve helped companies produceOffice 365 Showcases, which have a lively, trade show flair. Kiosks are set up in a cafeteria, meeting room or other convenient location. Hosting each kiosk is a departmental Office 365 Power User who demonstrates a unique aspect of the software to everyone who stops by.Read more about how to make Office 365 Change Management and End User Adoption Fun

  • PXE boot tablet with Used USB dongle

    We are running SCCM 2012 R2 Single Primary Site Server.
    We are using the dongle (USB) to PXE boot the tablet computer.
    We have advertised the Task Sequence to All Unknown Computer.
    Once we use the USB dongle to image computer 1 , then the MAC address of USB dongle gets associated with the computer name of the tablet because the tablet does not have Ethernet port.
    Now to image computer 2 if we PXE boot with used dongle gets PXE abort as it is known computer.
    If we advertise to "All Known" computers then try the PXE boot works and we can image computer2 .
    Now how can we advertise task sequence to "All Unknown" computers and get the task sequence to work with used USB Dongle.

    I suggest going back and reading it again then.
    Highlight:
    A “better” solution could be to create a collection, that is based on the Mac Address of the devices, which are used to deploy those systems. So typically this collection will have a handful of Mac Addresses. Important part is, that those Mac addresses
    shouldn’t be used in day to day business, just for the plain purpose of deployment. Then one can advertise as many task sequences as required and limit the deployment(s) to only media and PXE. This way, the deployment isn’t visible from the Software Center
    but the support staff can continue to deploy new systems using PXE or other medias like USB Sticks.
    Don't retire TechNet! -
    (Don't give up yet - 12,830+ strong and growing)

  • Boot Error with grub installed...no debug instructions

    * Quick Intro / About *
    Hello everybody... im new to linux in general and arch caught my eye since i have an interest in learning programming... i figured arch's documentation was better than that supplied for ubuntu since it's more in depth and has the core utilities needed to get a base system running with in-depth explanations (which i like). trust me when i say, i have read almost all of the arch documentation more than
    a few dozen times and have completed this successfully before...
    * My Problem *
    I installed my copy of Arch with the Core Utilities package and followed the wiki guides to the tee. i've done several test installations with VMware and Virtualbox OSE and decided to do it for real on my Toshiba Laptop Satellite l305d-s5895... all my hardware is currently supported by the majority of the Linux Distro's (i did my homework). I am attempting to do a dual boot with Arch and Windows
    the "/etc/rc.conf" file
    Localization -> default
    Hardware -> default
    Network ->
    HOSTNAME="myhostname"
      the "/etc/hosts" file is automatically adjusted during install
    eth0="dhcp"
    INTERFACES=(eth0)
    gateway="dhcp"
    ROUTES=(!gateway)
    Deamons -> default
    filesystem setup
    win7 -> hd0,0 sda1 primary
    arch -> hd0,1 sda2 primary
    swap -> hd0,1 sda5 logical
    cdrom -> sbd (device is auto-mounted)
    /dev/sda (MBR / Single HDD Device)
    After Grub Configuration ...these are my options to select for grub mount point
    /dev/sda
    /dev/sbd
    /dev/sda
    /dev/sda1
    /dev/sda2
    /dev/sda5
    /dev/sbd
    I always select /dev/sda at the very top of the list...
    the "/boot/grub/menu.lst" file
    Gen Config ->
    timeout 5
    default 0
    color light-blue/black light-cyan/blue
    Boot sections ->
    # (0) Arch Linux
    title KDM
    root (hd0,1)
    kernel /boot/vmlinuz26 root=/dev/sda2 ro vga=ask
    initrd /boot/kernel26.img
    # (1) Fallback (default settings)
    # (2) Windows
    title Windows 7
    rootnoverify (hd0,0)
    #makeactive #win7 does not require this
    chainloader +1
    * the Error I recieve *
    At boot and during reboot, unless i have a boot medium, this is what i am prompted with...
    Intel UNDI, PXE-2.1 (build 082)
    Copyright (C) '97 - '00 Intel Corp.
    For Realtek RTL8101E/8102E PCI-E Ethernet Controller v1.05 (071227)
    PXE-E61: Media test failure, check cable
    PXE-M0F: Exiting PXE ROM.
    No bootable device -- insert boot disk and press any key
    any help would be amazing! i have no idea why at boot the computer searches for a network connection
    instead of the GRUB! >.<
    i am able to boot however with the Arch Live Disc and access my filesystem for both Arch and Windows 7
    and resume normal use!

    well, just as an update... i believe it is a software issue... i wiped my whole HDD with gparted and set the partitions with Arch Live Core Install medium and GRUB worked perfectly... i created an NTFS partition as well for Win 7... hopefully the Win Installer wont overwrite GRUB and use its own bootloader. i was re-reading an area of the wiki and found...
    - GRUB must be installed on the MBR (first sector of the hard disk), or the first partition of the first storage device to be recognized by most BIOS's.
    source: https://wiki.archlinux.org/index.php/Gr … stallation
    hopefully i can just reinstall GRUB if needed with the Live Disc and i can boot win7 and arch like that...
    if an suggestions, or comments, please...would be nice.
    Last edited by xovertheyearsx (2011-03-11 05:23:05)

  • Surface Pro 3 PXE Boot Error

    Hi there,
    I am using MDT 2013 on a WDS 2008 R2 and everytime i tried to image the tablet via PXE boot through the Surface Pro 3 ethernet adapter, i get this error:
    Wizard Error:
    A connection to the deployment (my deployment share) could not be made.
    The following network device did not have a driver installed.
    PCI\VEN_11AB&DEV_2B38&SUBSYS_045E0001&REV_00
    Retry: Try again to connect to the deployment share.
    Cancel: Give up, cancelling any in-progress task sequence.
    PLEASE HELP!

    I bought a Belkin USB2.0 adapter and connected to my Pro 3 while the Pro 3 ethernet adapter is connected as well. So 2 network cables are needed. I pxed boot using the Pro 3 ethernet adapter and deploy the image using the Belkin2.0 adapter. Error didnt
    come back and deployment was successful. I mean this is a workaround but it works in my environment. The Belkin2.0 drivers are in WinPE and MDT.

  • Failed to Create MDT Boot Image in SCCM 2007

    Hello Everyone,
    I am trying to create MDT Integrated Boot Image in SCCM to Enable DART Integration on it. But when i try to Create Boot Image it Fails with below Error Message.
    Started processing.
    Creating boot image.
    Copying WIM file.
    Mounting WIM file.
    WIM file mounted.
    Setting Windows PE system root.
    Set Windows PE system root.
    Set Windows PE scratch space.
    Adding standard components.
    Adding extra content from: C:\Users\ADMINI~1\AppData\Local\Temp\1\i5wqsynb.efm
    Unmounting WIM.
    Copying WIM to the package source directory.
    Creating boot image package.
    Error while importing Microsoft Deployment Toolkit Task Sequence.
    Failed to insert OSD binaries into the WIM file
    Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The ConfigMgr Provider reported an error.
    ---> System.Management.ManagementException: Generic failure
    at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
    at System.Management.ManagementObject.Put(PutOptions options)
    at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
    --- End of inner exception stack trace ---
    at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
    I have searched over Internet for the same Error and I guess it was a Permission Issue. But my Environment is as below.
    AD & SCCM Server on Same Machine
    Folder have Full Permissions to SYSTEM, SCCMComputerAccount, DomainAdministrators, and Even I gave to Everyone Full
    Control.
    This is a LAB Environment with No Antivirus, No UAC
    ANY HELP ON THIS Folks..... (:-()
    Ram

    Hi Ychinnari,
    As your question is related to SCCM report. it is not supported here.
    you could post it in SCCM forum for better supports, Thanks for your understanding.
    SCCM forum link:
    https://social.technet.microsoft.com/Forums/systemcenter/en-US/home?category=configurationmanager
    Best regards,
    Youjun Tang
    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.
    Click
    HERE to participate the survey.

  • 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.

  • Photoshop Elements 8.0: deplovment with SCCM 2007

    Hello
    We are currently planning the transition to Windows 7 Enterprise.
    The deployment will take place with MS SCCM 2007 - we could not find any policies regarding this case.
    We need to know if Photoshop Elements 8.0 with the following client applications, SCCM and standard user-rights is running.
    Used software products / local application deployed on clients:
    • Microsoft Windows 7 Enterprise
    • Internet Explorer 8.0
    • Adobe Flash Player 10.0.32.18
    • Adobe Shockwave Player 11.5.2
    • Adobe Acrobat Reader 9.2
    • Windows Media Player 12.0
    • Microsoft Office 2007 Enterprise mit SP2
    • Sun Java Runtime Environment (JRE) 6.17
    • Microsoft .NET Framework 3.5
    • Ghostscript 8.7
    • Software-Deployment: Microsoft SCCM 2007 R2 SP2
    • Server-Plattform: Microsoft Windows Server 2008R2
    • Standard User-Rights
    We ask for verification of requirements, whether the necessary conditions are met by PSE 8.0.
    Best wishes,
    Simon

    Hi Simon,
    I would request you to contact the Adobe Tech Support/Customer Care team and they should able to provide a confirmation on these queries.
    As per my knowledge, we dont impose any explicit restrictions on PSE working with Ms SCCM 2007/Server 2008/ or with Standard User Rights.
    But for installing PSE and doing a certain operations, you need to have admin rights.
    Again, I would request you to get in touch with support team and get a confirmation.
    Regards,
    Ankush

Maybe you are looking for

  • How do you check what your user ID and password is?

    hey, anyone know how for me to find out my user id and password? I need them to start up my mail account and to download a program. I called apple but they said to either ask here or I'd have to extend my phone support, and thats too expensive for me

  • WTK 2.5.x and Emulator.exe

    Hi, I'm having a problem with the 2.5.x wireless toolkits. When I run them from the command line. With all the correct settings, including skins etc. I.e. emulator.exe -Xheapsize:2M -Xdevice:testdevice -Xdescriptor:game.jadI get a stack overflow exce

  • SQL LOADER and ORA-01861: Please ignore,,my mistake...its duplicate

    Hi, I've to load data through control_file(.ctl) into oracle table through sqlldr. Oracle 11g, win xp. as soon as I use - sqlldr dss/dss control=orders.ctl I get error or nothing. Text file that is generated after loading fails has the following erro

  • Restoring from back up

    if i have a copy of an old back up file from the mobilesync file in my computer, could i delete the one that is in the file now and replace with an old one to restore from?

  • Acrobat DC - export all images

    In the previous version you could export all images in a pdf-document through the menu: Tools > Document Processing > Export All Images Adobe Acrobat X Pro * Export images to another format Is it still possible to do in Acrobat DC ? Thank you for any