Jump to content


Search the Community

Showing results for tags 'in-place upgrade'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 3 results

  1. I have been tasked with upgrading roughly 800 PCs in my environment from Windows 7 to Windows 10. One problem that I am discovering is that we have multiple versions of Windows 7(Home, Pro and Enterprise). Professional is overwhelmingly most common, tho as we are trying to use bitlocker, we need to use Enterprise. I built the TS using the instructions located here https://docs.microsoft.com/en-us/windows/deployment/upgrade/upgrade-to-windows-10-with-system-center-configuraton-manager and it seems to work pretty well on Win7 Enterprise > Win 10 Enterprise so long as i remove System Center Endpoint Protection first. When I attempt to upgrade a Win7 Professional pc i get the attachedsetuperr.log Is there an upgrade path available that I can use to take Win7 Pro to Win10 Enterprise?
  2. Microsoft explains that an in-place OS upgrade from Server 2012 to Server 2012 R2 is supported (let's make that clear before someone pulls out the backup / reinstall / site recover copypasta, ok?) for a site server running Config Manager 2012 R2 SP1. So, I did just that, and after wrangling with some problems with WSUS, the site server is working as intended. Yes, even WSUS is working properly; I had to fix some site binding problems and edit the web.config to support Windows 10 clients, but that was it. I had to do the in-place upgrade because WSUS 3 broke after a recent Windows 10 update, and the fix was to update to WSUS 4, on Server 2012 R2. Some Remote Console users can't log on to the site server now, though. These users are not domain admins, but they are SMS admins; the site server's SMS Admins local group lists our IT Department's domain global group as a member, and this group also has the site server's Full Administrator role. I dug further and found the site server's SMS Admins local group has needed permissions in DCOM, too. I haven't yet checked the other requirements. Members of the Domain Admins global group can use a remote console, so I think I can eliminate network and firewalling as a cause. It's just members of the SMS Administrators global group or our IT Department global group that aren't also Domain Admins can't use it. What other permissions should I check? While local non-admins don't normally have write access to the AdminUILog folder on the remote console, I can grant Modify access to it and get this output from the SMSAdminUI log. It's pretty generic, though: [7, PID:5448][08/15/2016 10:16:09] :System.Management.ManagementException\r\nAccess denied \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementScope.InitializeGuts(Object o) at System.Management.ManagementScope.Initialize() at System.Management.ManagementObjectSearcher.Initialize() at System.Management.ManagementObjectSearcher.Get() at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.Connect(String configMgrServerPath)\r\nManagementException details: [7, PID:5448][08/15/2016 10:16:09] :Transport error; failed to connect, message: 'The SMS Provider reported an error.'\r\nMicrosoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe SMS Provider reported an error.\r\n at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.Connect(String configMgrServerPath) at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)\r\nAccess denied \r\nSystem.Management.ManagementException\r\nAccess denied \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementScope.InitializeGuts(Object o) at System.Management.ManagementScope.Initialize() at System.Management.ManagementObjectSearcher.Initialize() at System.Management.ManagementObjectSearcher.Get() at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.Connect(String configMgrServerPath)\r\nManagementException details: [7, PID:5448][08/15/2016 10:16:14] :System.Management.ManagementException\r\nAccess denied \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementScope.InitializeGuts(Object o) at System.Management.ManagementScope.Initialize() at System.Management.ManagementObject.Initialize(Boolean getObject) at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options) at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
  3. Hi, I had old installation of sccm 2012 r2 sp1 on 2008 r2 with sql 2008 r2 on same server. I wanted to start deploy windows 10 (1703) but it turned out that this version is supported only on newest SCCM 1702. So I have upgraded sccm 2012 to 1606 using baseline media and then to 1610 using sccm console in administration section. Then I have installed 2 patches which were issued to 1610. I checked if installation of 1702 will pass but it failed. Then I have done OS upgrade from 2008 r2 to 2012 r2: - I have backed up sccm using backup task and manually triggered service to start backup now. Afterwards backup task was disabled. - I disabled all automatically started services of SMS* for the time of upgrade - I then started in-place upgrade of OS. It turned out fine. Couple problems have emerged but they were quickly solved. - Then I have reenabled SMS* services back to automatic start - Rebooted the server and wanted to enter sccm console but then... Console says it cannot connect to site <site code and address>. Also some information regarding sms provider is shown. Just generic error for console itself. Nothing can be done from the console now. Just before upgrade of OS it was working ok. In Event Viewer there are some errors regarding: 1) Event filter with query "SELECT * FROM __InstanceOperationEvent WHERE TargetInstance ISA "ccm_siteassignment"" could not be reactivated in namespace "//./root/ccm/Policy/Machine" because of error 0x80041010. Events cannot be delivered through this filter until the problem is corrected. 2) The server {GUID} did not register with DCOM within the required timeout. 3) The WinRM service is not listening for WS-Management requests User Action If you did not intentionally stop the service, use the following command to see the WinRM configuration winrm enum winrm/config/listener 4) Transport error; failed to connect, message: 'The SMS Provider reported an error. '\r\nMicrosoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe SMS Provider reported an error Our actions so far: 1) Add Local Activation for SYSTEM for SMS Agent Host in DCOM 2) Check that winrm enum winrm/config/listener output and see that all interfaces are mentioned there 3) Disabled firewall 4) Connected to our site db using SQL Management Studio For upgrade I have used those two guides: http://ccmexec.com/2016/03/configmgr-cb-1602-server-2008-r2-in-place-upgrade-to-2012-r2/ https://blogs.technet.microsoft.com/configmgr_geek_speak/2016/03/23/configuration-manager-1602-on-windows-2008-r2-sql-2008-r2upgrading-to-windows-2012-r2-sql-2014/ Current state: 1) Console is not working as it cannot connect to site (yes I'm starting it as an administrator using account which pre-os-upgrade was working correctly even from remote host) 2) Site system is 2012 r2: - fully updated, - sql server installed: 2008 r2 enterprise I don't have any more ideas how to fix this. Any help will be much appreciated. I can provide any logs which will be required. Just please give path where to find them. SOLUTION: 1) I have checked logs for AdminConsole (logs are located in: C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\AdminUILog\SmsAdminUI.log) Turned out that there was an error regarding wmi namespace and some other stuff so I have searched Internet for this particular error. I've found a thread regarding SCCM 2007 but still relevant. https://social.technet.microsoft.com/Forums/en-US/3f5f82a4-8ca1-492f-8ca0-44c94dbe547f/unable-to-open-sccm-admin-console?forum=configmgrgeneral 2) I have opened wmimgmt.msc and saw that in list of namespaces ineed root\SMS namepsace is missing. 3) Then in this post: https://social.technet.microsoft.com/Forums/en-US/7e0576dd-e588-403f-8af9-698f730d6813/unable-to-connect-remote-configuration-manager-console?forum=configmanagergeneral there was information on how to reconstruct the namespace using: mofcomp file.mof In my case, mof files were located in: C:\Program Files\Microsoft Configuration Manager\bin\X64 and not all but some. Still this was enough to reconstruct the namespace and reenable SCCM console to connect to site database. I just checked briefly the site in console and all my applications are still there so I suppose it'll be easier from now on to debug possible errors. I just hope that pxe is still working since I've seen somewhere that it might be broken after in-place upgrade.
×
×
  • Create New...