OS-Deployment to virtual servers with SCVMM 2012 R2 vs SCCM 2012 R2 or integration with both?

Hi,
OS-Deployment to virtual servers with SCVMM 2012 R2 vs SCCM 2012 R2 or integration with both?
Is SCCM just for physical servers, and SCVMM for virtual?
What are benefits of integrating them?
/SaiTech

Hi,
Please refer to the links below:
Introduction to Configuration Manager
http://technet.microsoft.com/en-us/library/gg682140.aspx
Virtual Machine Manager
http://technet.microsoft.com/en-us/library/gg610610.aspx
The System Center 2012 Integration Guide provides information about automating each of the System Center components and integrating them with each other and with other systems and applications.
For more information, see the
System Center 2012 Integration Guide.
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.

Similar Messages

  • Error in push sccm client CcmSetup failed with error code 0x80070643 ccmsetup sccm 2012

    i want to push sccm client for all computer i enable automatic side-wide client installation 
     some computer get error code 0x80070643
    ccmsetup sccm 2012 this 
    when i tray manual installation get same error and ccmsetup.exe stopped 

    Duplicate of
    https://social.technet.microsoft.com/Forums/en-US/3bac4677-46b0-4d96-b63d-a819efcc7f35/error-in-push-sccm-client-ccmsetup-failed-with-error-code-0x80070643-ccmsetup-sccm-2012?forum=configmgrgeneral
    Please don't double post.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • SCCM 2012 SP1 to SCCM 2012 R2 - Side by Side

    Hi Friends,
    Currently our SCCM infrastructure is running with a CAS site, 2 Primary Sites and 8 Secondary sites with SCCM 2012 SP1. Now we want to update this infrastructure from SCCM 2012 SP1 to 2012 R2. But we want remove CAS site and to keep only single Primary Site.
    Can this be done in Side by Side migration from SCCM 2012 SP1 to SCCM 2012 R2 ? If yes then please suggest how to migrate all data (Packages/Clients) from SCCM 2012 SP1 to new infra on SCCM 2012 R2.
    Thanks in advance.

    You don't have many (supported) options here. Detaching a site is not possible, so indeed your only option left is to migrate. Problem here is that the supported scenario is from a ConfigMgr 2012 R2 site to a ConfigMgr 2012 R2 site (see:
    http://technet.microsoft.com/en-us/library/gg682006.aspx). That means you should first upgrade your old environment before you can start with your migration.
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • Migration of SCCM 2012 SP1 to SCCM 2012 R2 in a new domain.

    I am wondering if it is possible to migrate objects from a SCCM 2012 SP1 server in one domain to a new SCCM 2012 R2 server in another domain ?
    I read this article, but it does not state this particular combination.
    http://technet.microsoft.com/en-us/library/gg682006.aspx
    Thx
    Thomas

    For Migrate from SCCM 2012 SP1 to SCCM 2012 R2 in same environment/Domain, it's support and applicable.
    But migrate to new domain, it's not support. Also you can't migrate database for new domain or object. you will need to rebuild it.
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical | Twitter:
    Mai Ali

  • SQL Server 2012 deployment with System Center Configuration Manager (SCCM) 2012

    hi,
    we have tried to deploy the SQL Server 2012 to our development machines with SCCM 2012 without success.
    Commandline parameters or Configuration.ini in either case the installation failed without any useful errorlog.
    Exists any howto which covers this scenario?
    regards
    genne

    Hello,
    Please see the following article about some requirements for SQL Server instances intended for SCCM 2012:
    http://www.sqlcoffee.com/Tips0019.htm
    Could please check to see if a Summary.txt log file exists after those installation attempts? The following article may help you locate the file on disk:
    http://technet.microsoft.com/en-us/library/ms143702(v=sql.110)
    Please share this log file with us, if possible.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Problems with E531 network drivers in SCCM 2012 R2

    We are having some serious issues with SCCM 2012 R2 operating system deployment (Windows 7) and the Thinkpad Edge E531 laptop - network drivers are not being applied during the imaging process. Do SCCM driver packages exist for this laptop?
    I downloaded the ethernet drivers manually from here, extracted the files from the executable, imported the drivers into SCCM (it found them), and created a driver package for this model. I also added the drivers to the boot images.
    I do not have an issue during the PXE phase, it is only during the Windows phase - and the laptop is unable to join the domain because it does not have network drivers. 
    In the OSD Task Sequence, I have tried both the auto-apply device drivers rule (default), and creating a special rule for Lenovo E531 with the WMI query: SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "%6885YU%" . The task sequences all work perfectly on virtual machines, so I am fairly certain this is a driver issue. I have tried Windows 7 x86, x64, and Windows 8.1 x64.
    Any thoughts are welcome - I am new to this particular school district and have never deployed Lenovo in my previous environments. I am about to select a model for this year's laptop purchases and at this point, I am backing away from Lenovo due to this issue.

    We do not create SCCM driver packs for the Edge line of products.  As an alternative you can use Update Retriever to download hardware drivers for a selected model and then use the Export feature to create a folder containing the source files for the drivers.  This can then be used in the Driver Import Wizard which will locate the INF files and only import the files referenced by the INF files.
    You mention you are using SCCM 2012 R2.  This means you should be using the Windows ADK for 8.1 which also means your boot images should be using Windows PE 5.  For your boot images you should be using the Windows 8.1 driver (http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/herr01ww.exe)
    In your OSD task sequence you need to be deploying Windows 7 drivers (http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/her101ww.exe)
    Make sure you keep these separate.  Meaning you should have a driver package for the Windows 7 drivers that you reference in an Apply Drivers task and this package should not include the Windows 8.1 drivers.  Add just the 8.1 drivers to the boot image.

  • Windows 8.1 Update (with WinPE 5.1) ADK + SCCM 2012 R2 and WinXP

    Hello,
    I see new ADK version (8.1 Update) is released
    http://www.microsoft.com/en-US/download/confirmation.aspx?id=39982
    It contains WinPE 5.1 and new USMT (which version?), does it support migration from WinXP to Win7?
    Previously I used USMT5 (instead of 6.3) and modified WinPE 5.0 with bootsect.exe from WinPE 4.0 (from ADK 8.0) on SCCM 2012 R2 CU3.
    And can I use ADK 8.1 Update with SCCM 2012 R2?

    He does answer your question about the USMT version.
    The rest still applies in terms of XP support. See below.
    http://blogs.technet.com/b/mniehaus/archive/2014/01/09/migrating-from-windows-xp-to-windows-8-1-using-mdt-2013.aspx
    Yes, ConfigMgr 2012 R2 is supported.
    http://blogs.technet.com/b/configmgrteam/archive/2014/04/03/understanding-the-adk-for-windows-8-1-update-and-configmgr-osd.aspx
    Daniel Ratliff | http://www.PotentEngineer.com
    in the article I found:
    Windows PE version 5.1 is not needed for Configuration Manager and can actually be problematic if you try to use it. Windows PE 5.0 can continue to be used to deploy Windows 8.1 Update. There is a documented process to upgrade Windows PE to version 5.1,
    but this should be considered incompatible with Configuration Manager at this time.
    So for a new installation of SCCM 2012 R2 I can install ADK 8.1 update because in contains WinPE 5.0 and option to update to 5.1. And unclear about XP, it seems XP is not supported again.
    Also fourth release was in September 2014, but article was posted in April 2014.

  • Helix gen.2 very slow with USB 3.0 and SCCM 2012 OSD

    Hello there, i have a problem with our Helix gen.2. i would like deploy the OSD with SCCM 2012 and so i insert the USB 3.0 Dongle driver in WinPE. The Download and WIM installation is very fast but slows down after the OSD TS insert all Drivers for the system an makes a reboot. After the reboot the machine runs very slow over the network (1GB) and over 20 Hours and breaks down with a unsigned Error Message 80004005. i change the driver to an old version for the UBS 3.0 but it doesn´t helps so i need help from you. with best regards andré

    What OS are you deploying on the box, 7 or 8.1?
    Did you import the drivers from the Helix2 SCCM driver pack for the appropriate OS into a Driver Package?
    Did you also add the USB 3.0 drivers specific to the OS being deployed into that same Driver Package?
    Do you have an Apply Drivers task that references this driver package in the task sequence?  If so, you should be able to find the task ID in the SMSTS.log file and verfiy it is running.

  • Help with Linking A Report in SCCM 2012

    I've got a report that shows us Flash Players Versions by Count. I'd like to be able to create a linked report that shows the specific computers that have a specific version. The current report looks like this
    I'd like to be able to click on a link in the Version column that would display the result of this somehow.
    Are any SCCM 2012 reporting gurus out there that have done something like this?
     For example, I'd like a link from the Version field to run a report that
    Orange County District Attorney

    My first recommendation is to adjust the query you are currently using as it will only show you x86 software titles.
    As for how to do it, that is easy (sort of). Write your two reports,Make sure that your second report have prompts of everything that you want to pass to it.
    Now are you sign BIDS or RP to create your reports? You need to know this as it is a lot harder to do this with RB vs BIDS.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • Applocker with Windows Installer rules and SCCM 2012

    Hi,
    We have been running Applocker since two years on Windows 7 Enterprise clients with SCCM 2007 as management and distribution tool.
    This setup was working fine until we migrated to SCCM 2012 and started to encounter problems with msi-packages not being able to self-heal when the source was the sccm client cache.
    We have recreated this scenario in a lab environment.
    Our setup is this:
    Windows 2008 R2 (DC)
    Windows 7 Enterprise SP1 (Client)
    Standard user (not admin)
    SCCM 2012 R2 (upgraded from 2007)
    Applocker with these rules:
    Executable Default rules enabled (Enforced)
    Windows Installer Default rules enabled (Enforced)
    Exception for %WINDIR% (where SCCM cache is located)
    Script Default Rules enabled (Enforced)
    Application msi-package with self-heal (omus) and advertised shortcuts
    We install the application from the sccm cache (%windir%\ccmcache) and then trigger a self-heal (user components being copied to the user profile).
    What we see on the client is: Error 1718. File C:\Windows\ccmcache\54\application.msi was rejected by digital signature policy.
    Event log is showing: Event 1008: The installation of
    C:\Windows\ccmcache\54\application.msi
    is not permitted due to an error in software restriction policy processing. The object cannot be trusted.
    It looks like the file cannot be evaluated by Applocker and therefore is not trusted. We get an Access Denied error when testing AppLocker-policy with the following PS-command,
    Get-AppLockerPolicy -Effective | Test-AppLockerPolicy -Path C:\Windows\ccmcache\54\application.msi. This command works fine when accessing files in the cache-folder on a SCCM2007-client.
    For testing purposes we recreated a similar folder structure: C:\Windows\Folder1\Folder2\application.msi where the user has no permissions on Folder2 and read on the other folders and the File.msi.
    This is how the permissions look like in SCCM 2012 (no user permissions on %Windir%\ccmcache). Applocker cannot evaluate the trust-level of application.msi.
    The GPO setting “Bypass traverse checking” is set to everyone.
    As we can see, the permissions are the same on SCCM 2007 client cache (%Windir%\syswow64\ccm\cache) but we do not have this issue there.
    Has anyone got Applocker (with windows installer rules actived) to work with SCCM 2012 and windows installer self-heal?

    More info. I found some people also encounter this same issue, but specific msi, take a look at
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/2ad92754-f01e-410e-97db-7a9bc81586db/msiinstaller-event-1008-when-trying-to-install-3ds-max-2011-after-group-policies-apply-on-domain?forum=winserverGP
    Juke Chou
    TechNet Community Support

  • [SCCM 2012 R2] How SCCM 2012 handles Software Update Revisions?

    Hi All,
    There are a lot of questions regarding how SCCM 2012 handles Software Update Revisions.
    Does anyone know what happened if:
    Windows update publish some update with revision #1
    Same update downloaded and deployed via SCCM 2012
    Windows update publish same update with revision #2 or any newer revision
    What is happening with SCCM and already deployed and downloaded revision? How should I know what revision is really on my distribution points?
    Thank you in advance.
    Regards,

    In WSUS Revision History is very simple:
    Where I can find revision history in SCCM??? (please do not mention dates):
    Possible scenario in SCCM:
    Windows update publish revision #1 for one update
    SCCM Download and Deploy same update and revision #1
    Windows update change revision to #2
    What SCCM does after this scenario?
    Auto update Distribution Points with new revision of already deployed and downloaded update?
    Clearly state in SCCM Console that there is new revision of already deployed and downloaded update and waiting for admin to act?
    Just update the revision in SCCM Console and leave old revision od Distribution Points?????

  • MS SQL Server 2012 Updates via SCCM 2012 R2

    I'm trying to determine if SCCM 2012 R2 can manage and deploy Hotfixes, Updates and Service packs for SQL Server 2012. Can someone please confirm that SCCM can manage this, how to download SQL Server Hotfixes, Updates and Service Packs into SCCM and where
    I can find instructions on setting up my MS SQL Server computers to receive SQL updates from SCCM.
    Thanks. 

    ConfigMgr absolutely can deploy updates and service packs for SQL. You just need to choose the versions you want in Software Update Point Products and Classifications. It's no different than deploying any other Microsoft updates.
    http://www.gerryhampsoncm.blogspot.ie/2013/04/sccm-2012-sp1-step-by-step-guide-part.html
    Is it a good idea? I don't think so. I think SQL updates should be part of a carefully planned (and tested) manual upgrade.
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • SQL 2012 SP1 and SCCM 2012 SP1

    Hi,
    I am installing SCCM 2012 SP1 with SQL 2012 SP1 in Stand-Alone mode. But I am receiving error:"the service broker endpoint cannot listen on port 4022 because it is in use by another process"
    I saw in SQL (SQL Server Configuration Manager) that I am using port 4022 without dinamic port.
    Thaks.
    Lessandro Zampieri - http://lezampieri.com

    Thanks for the reply.
    C:\>netstat -ano
    Active Connections
      Proto  Local Address          Foreign Address        State           PID
      TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       780
      TCP    0.0.0.0:443            0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:4022           0.0.0.0:0              LISTENING       4664
      TCP    0.0.0.0:5985           0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:47001          0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING       528
      TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING       836
      TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING       900
      TCP    0.0.0.0:49155          0.0.0.0:0              LISTENING       624
      TCP    0.0.0.0:49156          0.0.0.0:0              LISTENING       624
      TCP    0.0.0.0:49217          0.0.0.0:0              LISTENING       616
      TCP    0.0.0.0:49219          0.0.0.0:0              LISTENING       4184
      TCP    0.0.0.0:49389          0.0.0.0:0              LISTENING       2056
      TCP    0.0.0.0:49627          0.0.0.0:0              LISTENING       5060
      TCP    127.0.0.1:49390        0.0.0.0:0              LISTENING       2056
      TCP    127.0.0.1:49628        0.0.0.0:0              LISTENING       5060
      TCP    127.0.0.1:57593        0.0.0.0:0              LISTENING       4664
      TCP    192.168.100.30:139     0.0.0.0:0              LISTENING       4
      TCP    192.168.100.30:445     192.168.100.20:49420   ESTABLISHED     4
      TCP    192.168.100.30:445     192.168.100.20:49421   ESTABLISHED     4
      TCP    192.168.100.30:445     192.168.100.20:49422   ESTABLISHED     4
      TCP    192.168.100.30:445     192.168.100.20:49423   ESTABLISHED     4
      TCP    192.168.100.30:4022    192.168.100.30:61430   ESTABLISHED     4664
      TCP    192.168.100.30:4022    192.168.100.30:61496   ESTABLISHED     4664
      TCP    192.168.100.30:49627   192.168.100.40:55914   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55915   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55921   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55922   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55926   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55927   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55928   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55929   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55930   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55967   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55992   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:55998   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56001   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56002   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56009   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56077   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56211   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56656   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56687   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56817   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56891   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56946   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:56959   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57027   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57072   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57223   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57240   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57248   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57268   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57292   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57293   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57294   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57311   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57312   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57314   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57320   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57340   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57342   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57343   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57369   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57372   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57379   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57385   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57386   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57387   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57388   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57389   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57390   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57391   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57392   ESTABLISHED     5060
      TCP    192.168.100.30:49627   192.168.100.40:57393   ESTABLISHED     5060
      TCP    192.168.100.30:61430   192.168.100.30:4022    ESTABLISHED     4112
      TCP    192.168.100.30:61496   192.168.100.30:4022    ESTABLISHED     4112
      TCP    192.168.100.30:61537   192.168.100.10:49158   TIME_WAIT       0
      TCP    [::]:80                [::]:0                 LISTENING       4
      TCP    [::]:135               [::]:0                 LISTENING       780
      TCP    [::]:443               [::]:0                 LISTENING       4
      TCP    [::]:445               [::]:0                 LISTENING       4
      TCP    [::]:4022              [::]:0                 LISTENING       4664
      TCP    [::]:5985              [::]:0                 LISTENING       4
      TCP    [::]:47001             [::]:0                 LISTENING       4
      TCP    [::]:49152             [::]:0                 LISTENING       528
      TCP    [::]:49153             [::]:0                 LISTENING       836
      TCP    [::]:49154             [::]:0                 LISTENING       900
      TCP    [::]:49155             [::]:0                 LISTENING       624
      TCP    [::]:49156             [::]:0                 LISTENING       624
      TCP    [::]:49217             [::]:0                 LISTENING       616
      TCP    [::]:49219             [::]:0                 LISTENING       4184
      TCP    [::]:49389             [::]:0                 LISTENING       2056
      TCP    [::]:49627             [::]:0                 LISTENING       5060
      TCP    [::1]:49390            [::]:0                 LISTENING       2056
      TCP    [::1]:49628            [::]:0                 LISTENING       5060
      TCP    [::1]:57593            [::]:0                 LISTENING       4664
      UDP    0.0.0.0:123            *:*                                    948
      UDP    0.0.0.0:500            *:*                                    900
      UDP    0.0.0.0:1434           *:*                                    3000
      UDP    0.0.0.0:4500           *:*                                    900
      UDP    0.0.0.0:5355           *:*                                    124
      UDP    127.0.0.1:51181        *:*                                    4132
      UDP    127.0.0.1:51338        *:*                                    124
      UDP    127.0.0.1:55475        *:*                                    900
      UDP    127.0.0.1:59835        *:*                                    1628
      UDP    127.0.0.1:60840        *:*                                    3596
      UDP    127.0.0.1:62010        *:*                                    1816
      UDP    127.0.0.1:62390        *:*                                    4112
      UDP    127.0.0.1:64129        *:*                                    624
      UDP    192.168.100.30:137     *:*                                    4
      UDP    192.168.100.30:138     *:*                                    4
      UDP    [::]:123               *:*                                    948
      UDP    [::]:500               *:*                                    900
      UDP    [::]:1434              *:*                                    3000
      UDP    [::]:4500              *:*                                    900
    All things are correct?
    Att.,
    Lessandro Zampieri - http://lezampieri.com

  • Cost of Intune and SCCM 2012 r2 vs SCCM 2012 r2 ICBM

    Is there any research/info on pros and cons of SCCM 2012 using intune for internet clinet management vs SCCM 2012 r2 and ICBM?  Things like cost, supportabiliy, etc.  I have seen intune vs sccm not Intune & SCCM vs SCCM and Internet Client
    Based Management. 
    Cyndy

    Hi,
    I think the reason is that you cannot manage Windows clients using the WIndows Intune Agent and integrate it with SCCM 2012. The integration with Intune and SCCM 2012 is for Mobile Device Management only so there is no possibility to install the Windows
    Intune Agent on a client and then manage it through the SCCM Admin Console.
    THe only scenario where that would work is if you manage a Windows 8.1 with the OMA-DM agent and enroll them in Intune as a mobile device with a limited set of features.
    So ICBM is still the way to go if you need all the features in SCCM or you want one console to rule them all.
    Regards,
    Jörgen  
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • Adding servers in to device collection in sccm 2012

    When I add a set of servers in to device collection some times some of the servers are failed to add in the collection. Is there any solution for adding the previously failed server again to the device collection successfully?

    Right click on collection and go to properties check whether added server is listed there or not? If no try to add the device manually by clicking yellow * button - put in server name ...next next and next very straight forward process.
    The first thing you need to do id update the collection after adding the server then only it may reflect. 
    What you meant by server get failed to add? Is there any particular error?
    Anoop C Nair (My Blog www.AnoopCNair.com)
    - Twitter @anoopmannur -
    FaceBook Forum For SCCM

Maybe you are looking for