DSDP 3.0 - CM 2012 R2 CU3 - Import Driver Packages Fail - Root element is missing

I realize that the Dell Server Deployment Pack 3.0 plug in is a vendor plugin to CM 2012 R2 but they (dell) are clueless.  So I am hoping that there is some knowledge here.
I've opened a case with Dell and have used the Dell forums to document my issue here:
http://en.community.dell.com/techcenter/systems-management/f/4469/t/19613996
(there are some pics that might help.)
I have a ConfigMan 2012 R2 environment where I have integrated the Dell Server Deployment Pack 3.0.  The installation succeeded and I have been able to also run the Dell System Integration using the DTK 4.4.  I am doing all of this work directly
on the CM 2012 primary site server.
However, when I try to Import Dell Drivers, I get an error in the wizard:
I have tried multiple OM DVD's each one produces the same results:
OM_SMTD_801_A00.iso
OM_SMTD_802_A00.iso
OM_SMTD_740_A00.iso
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Xml.XmlException: Root element is missing.
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   at System.Xml.XmlTextReaderImpl.Read()
   at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
   at System.Xml.XmlDocument.Load(XmlReader reader)
   at System.Xml.XmlDocument.Load(String filename)
   at Microsoft.ConfigurationManagement.OemDeployment.DellDriverPackageImport.PackageSelection.GetPackageListXml(String dellCatalogXml)
   at Microsoft.ConfigurationManagement.OemDeployment.DellDriverPackageImport.PackageSelection.PackageSelection_Load(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34014 built by: FX45W81RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
Microsoft.ConfigurationManagement
    Assembly Version: 5.0.0.0
    Win32 Version: 5.0.7958.1401
    CodeBase: file:///D:/Program%20Files/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.ConfigurationManagement.exe
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34239 built by: FX452RTMGDR
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
.... (log continues)....
Any ideas? 
My CM 2012 R2 is running on Windows 2012 R2.

Thanks for your comment. I thought that Microsoft might have had some involvement with the writing of this tool:
http://en.community.dell.com/techcenter/systems-management/w/wiki/4125.dell-server-deployment-pack-dsdp-for-configuration-manager

Similar Messages

  • SCCM 2012 OSD; Not finding driver package during deployment

    I've been having some trouble setting up my OSD deployment using SCCM 2012 and hope someone can point me in the right direction.  Specifically I am having trouble with device driver deployment while deploying my reference image. 
    I am running SCCM Config Manager 2012 SP1 CU2. This is running on a Server 2012 VM with SQL 2012.  I am building an OSD deployment and have successfully captured my reference image.  I am not sure if it matters, but I manually built a reference
    PC and using capture media (USB stick), I successfully captured my reference image.  I have imported my drivers for the target PC into Config Manager and into a driver package.  The driver package has been deployed to the distribution point
    (DP).  I checked the status of the driver package within the console and verified it has been deployed to the DP.   I created a new task sequence (TS) to deploy the captured wim.  Within the TS, I added an "Apply
    Driver Package" step and pointed it to the aforementioned driver package.  I added a WMI query to the step as follows
    select * from Win32_ComputerSystem where Model like "HP Probook 6570b%." 
    Incidentally, I did a wmi query on the target PC to verify the model.  I deployed the TS to the unknown computers collection and PXE booted the target PC.  I ran through the OSD wizard and while OSD is verifying the deployment prerequisites,
    the deployment fails with the error, "The task sequence cannot be run because a package referenced by the task sequence could not be found."  I checked the smsts.log log and found the following:
    Failed to find CCM_SoftwareDistribution object for AdvertID="CT120043", PackageID="CT100044", ProgramID="*"
    After some research I found this error means Config Manager cannot find the driver package (PackageID="CT100044")
    for deployment.  After more research I have done the following:
    Deleted the Driver Package and recreated it and updated the TS step to point to this package.
    Deleted and recreated the TS along with the driver package.
    Recreated the driver package and distributed content, only importing the NIC drivers as a way to make a simple test.
    When distributing content I verified it was successfully completed each time as per the console.
    Each time I recreated the driver package and the OSD failed, smsts.log is showing the appropriate package ID in the error.  If I disable the Apply Driver Package step and configure a Apply Device Drivers step to install the best matched compatible drivers
    and limit the driver matching to the specific driver package, the OSD completes but the drivers do not install. It is as if Config Manager is not seeing the imported drivers at all.
    I have run out of options to try and hope someone can help point me in the next direction to take.  After reading numerous forums and guides, I am sure I am doing the OSD steps correctly but I am apparently missing something.
    Thanks in advance,
    Mike G.

    Thanks for responding.
    Yes after I posted the question I right-clicked on the driver package, and selected to update distribution points.  I checked now (about 12 hours later) and the package is showing it has not finished updating.  I checked the content status and
    it is "waiting for content."  I looked at distmgr.log and I found an error "Failed to start DP health monitoring task for package 'CT100044'. Error code: -1".  This error would occur every 30 min after each time the DP retried to process
    the package. After some research I found a post stating a file called "Microsoft" or "Program" on located on the root of the site server could cause this and renaming or deleting the file would resolve this. I renamed the file and after the next time
    it retried, the error cleared, however the package status is still waiting for content.  I tried doing a validation on the package but so far there has been no change.

  • Re-importing a package fails

    Hi,
    usually, you can always re-import a package into OWB (10gR2) and synchronize it with the database. But I have the phenomenon that some (not all) packages fail in this process; after pressing Finish the import wizard dies and does almost nothing. I tracked it down to the the DebugSQL.000.log file and found as last entry:
    select line, text from all_source@owb_1335 where owner = 'DWH_ADMIN' and name = 'UTIL' and type = 'PACKAGE' order by line
    With other packages which do the re-import perfectly the next line would be the analogous query to read the PACKAGE BODY. This would indicate an overflow issue, but the package isn't big at all and works well when imported into another module. I cannot find any trace log of this failure. And - strange enough - the failing process is still able to drop the temporary database link owb_nnnn.
    Some ideas
    regards
    Thomas

    Hi Borkur,
    Dropping and re-importing the package would work well (works for another module) but this is a package whose procedures and functions are heavily referenced in several mappings and process flows (supports the custom job management). So, I would be forced to re-synchronize them all which I want to avoid. The other way would be to modify the package manually (only the signature is needed not the code since I will not deploy it from OWB, in fact, I deployed it from Oracle Designer !!!). But OWB Paris doesn't allow this. Once imported, always imported. You can modify imported tables, procedures, functions but not packages. Or is there a way ???
    regards
    Thomas

  • New-CMVhd error Not Found - SCCM 2012 R2 CU3

    When trying to execute New-CMVhd via powershell in SCCM 2012 R2 CU3 I get a "Not Found" error.
    This happens in our production and pre-production environments.
    Using the Console wizard works fine.
    Command is:
    New-CMVhd -Path "\\machine\D$\Windows2012R2Server_SCCM.vhd" -Name "Windows2012R2Server_SCCM" -Version "1.0" -VHDSize 100 -TaskSequencePackageId "XXX00123" -DistributionPointServerNames "server.contso.com" -Description "Built with Deploy Server To VHD Task Sequence." -Verbose
    Output:
    VERBOSE: Performing the operation "New" on target "Vhd: New".
    VERBOSE: Executing WQL query: Select * From SMS_TaskSequencePackageReference_All where PackageID='XXX00123'
    VERBOSE: Query options: None
    VERBOSE: Executing WQL query: Select * From SMS_DistributionPointInfo where Name='server.contoso.com'
    VERBOSE: Query options: None
    VERBOSE: Query 'Select * From SMS_DistributionPointInfo where Name='server.contoso.com'' processed 1
    results.
    VERBOSE: Executing WQL query: SELECT Distinct tspr.RefPackageID FROM SMS_TaskSequencePackageReference_All AS tspr WHERE
     tspr.PackageID='XXX00123' and tspr.RefPackageID Not In (SELECT PackageID FROM SMS_Package AS p WHERE
    p.PkgSourceFlag=1)
    VERBOSE: Query options: None
    New-CMVhd : Not found
    At line:1 char:1
    + New-CMVhd -Path \\machine\D$\Windows2012R2Server_SCCM.vhd -Name "Windows201 ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (Microsoft.Confi...s.NewVhdCommand:NewVhdCommand) [New-CMVhd], WqlQueryExc
       eption
        + FullyQualifiedErrorId : UnhandledExeception,Microsoft.ConfigurationManagement.Cmdlets.Osd.Commands.NewVhdCommand
    Can anyone else reproduce this? I have a feeling it will be a premier support call to Microsoft :-(
    Thanks

    Hi,
    Pls try to run the following command to import CM powershell module and change the path to be the CM server before your new-cmvhd command:
    import-module 'C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\ConfigurationManager.psd1'
    Set-Location CMserver:\
    “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.”

  • Office 2013 Professional Plus - 32 bit Deployment takes an unacceptable time to deploy in SCCM 2012 - SP1 CU3

    We recently migrated over to SCCM 2012 SP1 - CU3 the first of the year from SCCM 2007 SP2.  We have used SCCM in the past to deploy Office 2010 and had deployed Office 2013 to our IT Dept. before moving over to SCCM 2012.  The deployment went as
    expected.  Now that we are ready to start deploying Office 2013 to our corporate workstations, the deployment time is running 4.5 hours to 5.5 hours from the local site server DP.  I am afraid to find out what time we are looking at for remote DP's. 
    The three factors that are different is that our SCCM site server is virtual, it is running 2012 for the OS, and obviously SCCM 2012-SP1 - CU3.   We are using the same package source files.   Previous to a successful deployment we were
    seeing hash mismatch errors which MS support pointed us to the nic driver on the VM was using E1000E and to change it to a VMX something driver.
    So I guess my question is anyone else out there deploying Office 2013 ProPlus - 32 bit from this type of environment?  Our previous deployment time for office was a little over an hour (not five hours).  Any suggestions where to look to improve
    the deployment time? 
    I am expected to deploy this in one week and have been working on these issues for weeks.

    I see now that you are using a combination of scripts and ConfigMgr package/program.
    The AppEnforce.log file is for use with the new ConfigMgr Application model.
    Is there any reason that you don't use the new model for deploying Office 2013? It's a single step process and perfect for it. If you use the Office Customisation Tool you can customise what you like. The process will then uninstall Office 2010 and install
    Office 2013.
    This is how you do it
    http://www.gerryhampsoncm.blogspot.ie/2013/03/sccm-2012-sp1-step-by-step-guide-part_9368.html
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • New SCCM 2012 client machines still getting SCCM 2012 SP1 client not the new SCCM 2012 SP1 CU3 client

    Hi,
    I've successfully (as far as I can tell) deployed SCCM 2012 SP1 CU3 and all my existing clients are showing a client version of 5.00.7804.1400.  But when I setup a new client system recently I noticed that the client version was showing 5.00.7804.1000,
    and not 5.00.7804.1400. 
    For new client systems, do I need to redeploy the packages that were created for SCCM 2012 SP1 CU3 so that the new systems get the new SCCM 2012 SP1 CU3 client? 
    Thanks,
    Nick

    Hi,
    Here's some good information to look over:
    http://sccmfaq.wordpress.com/2013/09/24/sccm-2012-include-cu-in-osd/
    I haven't followed these instructions myself, since I haven't really had any good reason to include CUs during the initial installation process. I use this method instead and I've never run into any problems:
    http://www.ronnipedersen.com/2013/06/installing-sccm-2012-sp1-cu2-quick-start-guide/
    Don't retire TechNet! -
    (Don't give up yet - 12,575+ strong and growing)

  • SCCM 2012 R2 CU3 UPGRADE BROKE REMOTE ADMIN CONSOLE CONNECTIVITY

    I installed SCCM 2012 R2 CU3 on my site server but it broke a couple things. I've never had problems with SCCM upgrades before. The admin console works if you log into the site server and run it from there but not when you try it from anywhere else (another
    server or a workstation). When you open the admin console on the site server it does have the new version of 5.00.7958.1401. Of the five suggestions that appear when your console won't connect, here's what I know:
    1) the remote machines can all ping the site server (call it server 01)
    2) we know it's not my account that's a problem as I can open the console on the site server itself
    3) This problem happens on server 02, which I put the new admin console on. It also happens with other machines which still have the CU2 console
    4) Yes, I'm an admin role, shown by logging into the console on the site server
    5) I have another network where everything works. I have not put CU3 on it yet, of course. The WMI permissions on Root, Root\SMS, and Root\SMS\site_ABC are identical on both site servers yet it works on non-upgraded one and not on the upgraded one.
    WMI info-I can WMI connect from the site server to these other machines but not WMI connect from the other machines to the site server: not root, SMS, or SMS\site_ABC, nor cimv2, even though the permissions match what is on the working network.
    When I launch the console from the site server entries about loading the console loading ok are in SMSAdminUI.log, but when I try to launch the console from other machines no entries are made, even though I changed the SmsAdminSNapIN value to VERBOSE.
    I checked DCOM permissions and they are the same on both networks.
    Another issue that appeared with this upgrade: I can install the client upgrade to CU3 on other machines but on the site server it fails with "Internal Error 2503" and when you click OK it you get "Internal Error 2502".
    Ben JohnsonWY

    I'd suspected this WMI problem was only affecting our Server 2012 boxes. I compared RSOPs and noticed the ones having this problem were all under the same OU and getting few GPOs. Our GPO person found a GPO that has somehow become unlinked.  He relinked
    it. After a gpo update AND a reboot these machines start working again.  So CU3 did not cause this WMI after all.
    And yes, the CU2 consoles won't connect to a CU3 site server, you have to run the console upgrade.
    I fixed the "internal error 2503/2502" by doing this: open task manager, click details, end the explorer task (screen will look blank at first). Click File and select "start new task", enter "explorer.exe' and click the run as admin
    button. The msp for CU3 client installed and the screen looks normal again. I only saw this error on the site server and have never seen it before.
    Ben JohnsonWY

  • SCCM 2012 R2 CU3 PXE issue

    Hi,
    I have a SCCM 2012 R2 CU3 lab where pxe is not working, the clients are able to connect to SCCM server but the download gets stuck on the boot image & then it fails with the following error :-
    Don't find any specific error related to this deployment in SMSPXE.log.
    Thanks,
    Pranay.

    I've had some issues various places with NICs and the TFTP process.  One fix I implemented was to add the following registry entry:
    Location:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WDSServer\Providers\WDSTFTP
    Name: MaximumBlockSize
    Type: (REG_DWORD)
    Value range: 512–1456
    Base: (Decimal)
    I set it to 1024, but you need to determine what value works for your environment.
    This is documented here:
    http://support.microsoft.com/kb/975710/en-us
    Jeff

  • Thin Client reporting issues since SCCM 2012 R2 CU3 upgrade.

    Please forgive me, I'm a SCCM newbie. I'm having an issue with my Thin Clients reporting back to SCCM since I upgraded to 2012 R2 CU3.
    The only pertinent thing I find in any log is "RegTask: Failed to get registration state. Error: 0x8009000b" "GetRegistrationState failed (0x8009000b)" in the ClientIDManagerStartup.log
    If anybody has any tips, I would be more than appreciative.

    I have not run into this before, but have you validated that your management point is healthy?
    This thread has a couple things to try as well:
    https://social.technet.microsoft.com/Forums/en-US/0d2e369d-cd93-4145-8db3-e9943c99a4ae/client-property-set-to-no-application-deployment-not-working-issue-with-registering-to-mp?forum=configmanagergeneral
    Jeff

  • Part of a migration project from SCCM 2007 to 2012 SP1 CU3 - Updates no longer working and reporting not correct

    Been working on a migration from 2007 sp1 to 2012 sp1 cu3.  I first installed directly to sp1 but realized we had a few 8.1 clients being built so I added the cu3 mid-stream.  I moved over two small subnets and pushed out some clients.
      I was able to push out updates from the 2012 server for OS realted updates to a collection.  After CU3 I tried to do the same process with Office 2013 updates and it just seems to sit there with the enforcement state showing unknown in the report.
      Also I checked the version of client on the machines and they have the CU3 version but when I run a report to show client versions it does not show these machines with the latest version but version for sp1.  It's almost like my management point
    is not working.  (just guessing).  I checked in the component status and everything is showing green.  I tried a wbemtest on one of the clients in the collection for the targeted updates and that is coming back with acceptable results. 
    Not sure where to look next. 
    I am not real proficient in 2012 yet and still bumping my way along.  Any help reviewing specific logs, etc. would be appreciated.  I have been searching for a solotion for several days now.

    Hi,
    1.Please make sure the update deployment is show up on the Deployment tab(Assets and Compliance -> Overview -> Devices -> the specific client properties)
    2.Check PolicyAgent.log on the client to see whether the specific client have received the deployment policy. If not, try to run the Actions about software updates on the Configuration Manager Properties from the client.
    3.Examine UpdatesDeployment.log, UpdatesHandler.log. UpdatesStore.log on the client.
    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.

  • CCMSETUP not updating on SCCM 2012 SP1 CU3/CU4 primary site

    I have a SCCM 2012 SP1 CU3 primary site and i can't upgrade the local installed SCCM Client.
    The error I get in ccmsetup.log is:
    <![LOG[MSI: Setup was unable to register the CCM_Service_HostingConfiguration endpoint
    The error code is 80041002]LOG]!><time="15:44:22.408-60" date="02-08-2014" component="ccmsetup" context="" type="3" thread="2496" file="msiutil.cpp:300">
    <![LOG[MSI: Action 15:44:22: Rollback. Rolling back action:]LOG]!><time="15:44:22.562-60" date="02-08-2014" component="ccmsetup" context="" type="0" thread="2496" file="msiutil.cpp:314">
    <![LOG[File C:\windows\ccmsetup\{59A0EA77-D28C-4286-83A6-04BB57B9CDD6}\client.msi installation failed. Error text: ExitCode: 1603
    Action: CcmRegisterHostingConfiguration.
    ErrorMessages:
    Setup was unable to register the CCM_Service_HostingConfiguration endpoint
    The error code is 80041002
    ]LOG]!><time="15:45:00.798-60" date="02-08-2014" component="ccmsetup" context="" type="3" thread="2496" file="msiutil.cpp:872">
    <![LOG[Client installation has failed too many times. Ccmsetup will now abort.]LOG]!><time="15:45:00.830-60" date="02-08-2014" component="ccmsetup" context="" type="3" thread="2496" file="ccmsetup.cpp:7941">
    <![LOG[Successfully deleted the ccmsetup service]LOG]!><time="15:45:05.831-60" date="02-08-2014" component="ccmsetup" context="" type="1" thread="2496" file="ccmsetup.cpp:3320">
    <![LOG[InstallFromManifest failed 0x80070643]LOG]!><time="15:45:05.831-60" date="02-08-2014" component="ccmsetup" context="" type="3" thread="2496" file="ccmsetup.cpp:7086">
    <![LOG[CcmSetup failed with error code 0x80070643]LOG]!><time="15:45:05.832-60" date="02-08-2014" component="ccmsetup" context="" type="1" thread="2324" file="ccmsetup.cpp:10544">
    I have this on my primary and secondary servers as well.
    Is upgrading to R2 recommended and will that solve this issue ?
    When googling to this issue i found that there is a solution for this: remove MP, upgrade Client, install MP.
    But this is my primary and secondary and on secondary i am not allowed to remove the MP. It is hardcoded enabled.

    Try the following steps to specify the hotfix when installing the client.
    1. Open an elevated command prompt.
    2. Run a command line similar to the following – if CU3 has already been installed, the MSP file below should be on the site server, in the
    \\servername\SMS_SITE\Client\hotfix folder:
    \ccmsetup.exe PATCH=\Configmgr2012ac-sp1-kb2882125-x64.msp 
    Juke Chou
    TechNet Community Support

  • Import Solution Package (WSP) 2013 using VS 2012

    Anyone working/worked on SharePoint 2013 solution using VS 2012?
    I am trying to Import Solution Package (WSP) using VS 2012, but VS 2012 doesn't allow to import the solution. It throws an error with message saying that SharePoint Foundation/Server 2013 need to be installed on local system.
    I have also installed MS Office Developer tool for VS 2012, but VS still throws an error while Importing Solution Package.
    Please suggest steps to import WSP in VS 2012..

    Hi vaibhavi,
    Here is the list of steps given
    http://msdn.microsoft.com/en-us/library/ee231603(v=vs.110).aspx
    Please remember to click 'Mark as Answer' on the answer if it helps you

  • SCCM 2012 Sp1 CU3 support Windows 2012 R2 deployment?

    Hi,
    Sorry for so basic question, but I have read few docuemnts, blogs and official materials and I'm a bit confused. 
    In our organization we have SCCM Sp1 CU3. We are planning create and next deploy Windows 2012R2 Server images. On some documentations there is CU3 supports only application managment, inventory and so on. but there is nothing about image deployment. 
    So, my question is - I have to upgrade SCCM 2012 Sp1 CU3 to SCCM2012R2 to capture, build and deploy Windows 2012R2 system?
    Thank you.

    Yes, you do. See what's new with ConfigMgr 2012 R2
    http://technet.microsoft.com/en-us/library/dn236351.aspx
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • Migrate 2012 SP1 CU3 Primary Server to a new machine?

    Because of some issues I am having with my current primary site server, I would like to bring up a new server and decommission the old. 
    The old server is running on 2008 R2 and the new server will run on 2012 R2.
    Right now, I have two servers running CM 2012 SP1 CU3.  I plan to upgrade the entire hierarchy to 2012 R2 before I decommission the old server.
    Primary Site Server Site System Roles – Distribution Point, Endpoint Protection Point, Management Point, Reporting Services Point, Site Server, Site System
    Second Server Roles – Application Catalog, Distribution Point, Fallback Status Point, Management Point, Site System, Software Update Point, State Migration Point
    Can someone please help me understand the process that I should follow to make this successful?
    1 - Bring up the new server
    2 - Configure all settings on the new server
    3 – Install Site System Roles on the new server
    4 – Add SMS Provider to the new server
    5 – Uninstall Site Server Roles from old server
    What am I not thinking about?
    Is there a better way to do this?
    Thanks for any help

    Hi,
    For the Second Server with roles that could be an option to install a new server, and move the roles to that server.
    For the Primary Site server there is no possibiltity to setup a new Primary Site server and transfer the role to that server as you can with the other roles. The way to do that would be to do a backup of Configuration Manager on the Server running 2008
    r2 and restore it on the server running Server 2012 r2 as an inplace OS upgrade is not supported on a primary site server either.
    You haven't mentioned where you SQL server is located either if it is local or remote.
    If you have issued you could also install a new Primary Site and Migrate the objects from the old Primary Site and then reassign the clients to the new site.
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • Listing RDS 2012 R2 collections from powershell remote fails

    I'm trying to list different informations of a RDS server farm => from a remote client PC <=
    I do following but when typing the last command - I get an error.
    Knowing that that same command runs correctly when launched from an RDS server
    enter-pssession RDS-SERVER-XYZ.contoso.net
    import-module remotedesktop
    get-command -module remotedesktop
     Get-RDSessionCollection -ConnectionBroker RDS-BRK-1.contoso.net
     => fails with message :
     Cannot index into a null array.
     At C:\Windows\system32\WindowsPowerShell\v1.0\Modules\remotedesktop\Utility.psm1:54 char:9
     +     if ($_script_resource[$Id])
     +         ~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : NullArray
     Cannot index into a null array.
     At C:\Windows\system32\WindowsPowerShell\v1.0\Modules\remotedesktop\Utility.psm1:54 char:9
     +     if ($_script_resource[$Id])
     +         ~~~~~~~~~~~~~~~~~~~~~~
         + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
         + FullyQualifiedErrorId : NullArray
     Get-RDSessionCollection :
         + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
         + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Get-RDSessionCollection
    Listing RDS 2012 R2 collections from powershell remote fails / same commandlet from local RDS serevr works fine
    Am I missing something ?
    MCTS Windows Server Virtualization, Configuration

    Are the Windows Remote Management rules enabled on the inbound firewall of the RDSH server?
    If you are running multiple roles on the RDSH  server you may need to increase the size of the memory available for powershell remoting.
    Run Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000 with powershell as an admin and reboot.
    HTH,
    JB

Maybe you are looking for