Jump to content


khawkins

Established Members
  • Posts

    43
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by khawkins

  1. You're welcome, I remember pulling my hair out over that one for a long time. Will never forget it either.
  2. Yeah I get a valid IP and can ping the DP\PXE server when F8 in WinPE. I will run the attached script to see if it throws up any missing drivers.
  3. Hi all, I have been working on an issue for the last week relating to PXE booting . It seems to have happened when upgrading to 1706 CB and ADK 1709. I have updated the boot image in sccm and imported the new boot into WDS. All devices boot into PXE but restart after preparing network connections. F8 shows I am getting a valid IP and can ping the DP\PXE server. The boot image is 10.0.16299. We use Dell devices (E7450 Opti 9020 etc) Error Failed to download PXE variable file after retrials. Exit code=22. PxeGetPxeData failed with 0x8004016c smsts.log Troubleshooting; Uninstalled PXE, WDS and deleted the Remoteinstall folder. Reinstalled PXE point Redistributed boot image Can anyone tell me what I am doing wrong here? Thanks Kevin
  4. Thanks Gavin, Getting the assettag\serialnumber was the realitively "easy" part, getting the modelnumber was the bit I was struggling with. Naming convention - %Model%%AssetTag% The powershell script was the only way I could do this.
  5. It's straight forward to enable, there should be a lot of guides out there. Regards Kevin
  6. Hey JJJackson, Have you enabled powershell in the boot image? Also it's important you have it set just after the OS install step.
  7. Ok so I got this working after making a lot of work out of it. I hope this helps someone, here are my exact steps; Objective: Powershell script to rename workstation %MODEL%-%SERIALNUMBER% Here is the PowerShell script ******* $ModelNo = (Get-WMIObject -Class WIN32_ComputerSystem).Model.Split(' ')[1] $SerialNo = (Get-WMIObject -Class WIN32_BIOS).SerialNumber $WorkstationName = $ModelNo + '-' + $SerialNo # Workstations $TSEnv = New-Object -COMObject Microsoft.SMS.TSEnvironment $TSEnv.Value("OSDComputerName") = "$WorkstationName" ******** Within the task sequence, this step NEEDS to be AFTER the apply OS and before the domain join Create a package pointing to the .ps1, but do not create a program. Add a TS step as follows -Run PowerShell Script -Package = "package created earlier" -Script name = "scriptname.ps1" -PowerShell execution policy = bypass Thanks everyone for the help. Kevin
  8. I'm still not having much luck with this. I have created a package that points to the powershell folder, but with no program. Here is the script; ************ $ModelNo = (Get-WMIObject -Class WIN32_ComputerSystem).Model.Split(' ')[1] $SerialNo = (Get-WMIObject -Class WIN32_BIOS).SerialNumber $WorkstationName = $ModelNo + '-' + $SerialNo Rename-Computer -NewName $WorkstationName -Restart ********** I can confirm it works, as I have ran it manually on an OS and it renames and auto restarts. I then add a run command to the TS (just after the Apply OS step) with the command powershell.exe -file rename.ps1 -executionpolicy -bypass Which fails. I also added a run powershell step and select set to bypass, with the command line rename.ps1 Which also fails. Any ideas?
  9. Ok so finally figured this out. On the ScanAgent.log I was seeing a lot of "Sources are not current" messages. This led me to dig further and that the SUP MUST be in the default boundaries group, which I didn't know. It apparently is new to 1702?!?! Once I added the SUP to the default group clients started reporting in instantly! Hope this helps someone out there. Regards Kevin
  10. The Scan update log states that the "Software Updates client configuration policy has not been received, default settings will be used.". I'm very confused, as it is enabled on the default client policy as well as a custom client policy. Just wondering if this could be getting blocked by the AV? <![LOG[Software Updates client configuration policy has not been received, default settings will be used.]LOG]!><time="16:15:11.948-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="11236" file="scantoolpolicy.cpp:648"> <![LOG[- -Recovering persisted Scan requests...]LOG]!><time="16:15:11.948-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="11236" file="scanjobmgr.cpp:118"> <![LOG[CScanAgent::CleanDeletedUpdateSources- entered. This will clean any update sources for which policy no longer exists.]LOG]!><time="16:15:11.963-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="11236" file="cscanagent.cpp:1579"> <![LOG[Software update client config event __InstanceCreationEvent received.]LOG]!><time="16:17:01.015-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="3056" file="cscanagent.cpp:1220"> <![LOG[- -Recovering persisted Scan requests...]LOG]!><time="16:17:37.642-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="9292" file="scanjobmgr.cpp:118"> <![LOG[CScanAgent::CleanDeletedUpdateSources- entered. This will clean any update sources for which policy no longer exists.]LOG]!><time="16:17:37.658-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="9292" file="cscanagent.cpp:1579"> <![LOG[- -Recovering persisted Scan requests...]LOG]!><time="16:25:58.301-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="4148" file="scanjobmgr.cpp:118"> <![LOG[CScanAgent::CleanDeletedUpdateSources- entered. This will clean any update sources for which policy no longer exists.]LOG]!><time="16:25:58.353-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="4148" file="cscanagent.cpp:1579"> <![LOG[Message received: '<?xml version='1.0' ?> <UpdateSourceMessage MessageType='ScanByUpdateSource'> <ForceScan>TRUE</ForceScan> <UpdateSourceIDs> <ID>{349E5FC2-62B1-4624-8733-9C7EAC502719} </ID> </UpdateSourceIDs> </UpdateSourceMessage>' ]LOG]!><time="16:34:01.916-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="3360" file="cscanagent.cpp:1042"> <![LOG[*****ScanByUpdateSource request received with ForceReScan=2, ScanOptions=0x0000000a, WSUSLocationTimeout = 604800]LOG]!><time="16:34:02.837-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="3360" file="cscanagent.cpp:216"> <![LOG[Sources are not current]LOG]!><time="16:34:04.556-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="3360" file="utils.cpp:104"> <![LOG[ScanJob({7B191E15-CD28-4FE8-9578-D05F84B25036}): - - - - - -Locations requested for ScanJobID={7B191E15-CD28-4FE8-9578-D05F84B25036} (LocationRequestID={40869FF1-8BCF-4021-A1A0-7FCAF8ED9B71}), will process the scan request once locations are available.]LOG]!><time="16:34:06.713-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="3360" file="utils.cpp:477"> <![LOG[Software update client config event __InstanceModificationEvent received.]LOG]!><time="16:58:03.507-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="1384" file="cscanagent.cpp:1220"> <![LOG[- -Recovering persisted Scan requests...]LOG]!><time="17:37:16.987-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="4396" file="scanjobmgr.cpp:118"> <![LOG[ScanJob({7B191E15-CD28-4FE8-9578-D05F84B25036}): CScanJob::Scan - Recovered Scan request with LocationRequestID={40869FF1-8BCF-4021-A1A0-7FCAF8ED9B71}. It is still waiting for Locations, will process the scan request once Locations are available.]LOG]!><time="17:37:17.019-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="4396" file="utils.cpp:477"> <![LOG[CScanAgent::CleanDeletedUpdateSources- entered. This will clean any update sources for which policy no longer exists.]LOG]!><time="17:37:17.019-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="4396" file="cscanagent.cpp:1579"> <![LOG[- -Recovering persisted Scan requests...]LOG]!><time="09:38:43.471-60" date="06-08-2017" component="ScanAgent" context="" type="1" thread="6872" file="scanjobmgr.cpp:118"> <![LOG[ScanJob({7B191E15-CD28-4FE8-9578-D05F84B25036}): CScanJob::Scan - Recovered Scan request with LocationRequestID={40869FF1-8BCF-4021-A1A0-7FCAF8ED9B71}. It is still waiting for Locations, will process the scan request once Locations are available.]LOG]!><time="09:38:43.565-60" date="06-08-2017" component="ScanAgent" context="" type="1" thread="6872" file="utils.cpp:477"> <![LOG[CScanAgent::CleanDeletedUpdateSources- entered. This will clean any update sources for which policy no longer exists.]LOG]!><time="09:38:43.580-60" date="06-08-2017" component="ScanAgent" context="" type="1" thread="6872" file="cscanagent.cpp:1579"> <![LOG[- -Processing Scan Job TTL invalidity request]LOG]!><time="16:28:11.219-60" date="06-08-2017" component="ScanAgent" context="" type="1" thread="2804" file="scanjobmgr.cpp:610"> <![LOG[Message received: '<?xml version='1.0' ?> <UpdateSourceMessage MessageType='ScanByUpdateSource'> <ForceScan>TRUE</ForceScan> <UpdateSourceIDs> <ID>{349E5FC2-62B1-4624-8733-9C7EAC502719} </ID> </UpdateSourceIDs> </UpdateSourceMessage>' ]LOG]!><time="16:28:13.769-60" date="06-08-2017" component="ScanAgent" context="" type="1" thread="2804" file="cscanagent.cpp:1042"> <![LOG[*****ScanByUpdateSource request received with ForceReScan=2, ScanOptions=0x0000000a, WSUSLocationTimeout = 604800]LOG]!><time="16:28:13.769-60" date="06-08-2017" component="ScanAgent" context="" type="1" thread="2804" file="cscanagent.cpp:216"> <![LOG[Sources are not current]LOG]!><time="16:28:13.805-60" date="06-08-2017" component="ScanAgent" context="" type="1" thread="2804" file="utils.cpp:104"> <![LOG[ScanJob({60E34093-608A-479C-849B-82745C72A00E}): - - - - - -Locations requested for ScanJobID={60E34093-608A-479C-849B-82745C72A00E} (LocationRequestID={8711969D-99B1-48E3-8014-118A3BDD3EC0}), will process the scan request once locations are available.]LOG]!><time="16:28:13.974-60" date="06-08-2017" component="ScanAgent" context="" type="1" thread="2804" file="utils.cpp:477">
  11. Thanks bonVoyage, At what stage of the TS do you add the powershell script?
  12. Hi guys, I have read a few articles on this but I am struggling on how to get this to work. We have dell PC's\Laptops and we need to automate the name of a new device build with the format ModelNumber-SerialNumber eg. "E5550-JAJJAJA". I have MDT integrated and I am using the gather step to gather device info. I have set the OSDComputerName value to %MODEL%-%SERIALNUMBER% This isn't working, which I suspect is because the model name is usually "Latitude E5550". Am I going about this the right way? Should I be using gather or is there another option to automate this? Thanks Kevin
  13. Hi all, I am having an issue with clients contacting the SCCM SUP. This is a fresh install of SCCM 1702 on a server 2012 R2 and Windows 10 environment. All is working as expected, except even the Software Update Point. WSUS is on its own Server and SCCM talks to it and pulls in all the updates. I can create SU groups and used scheduled updates to inject the patches into my wim. BUT clients are not talking to SCCM SUP, all the updates have "0" required\installed against them. The environment did have WSUS for patching previously, so I have excluded all WSUS Group Policies, by blocking inheritance on the OU. I have enabled SUP in client settings and applied them to the clients. When I check the locationservices.log there is no trace of the "WSUS path=http://" telling the clients to go to their SCCM SUP server. Also the clients do not have any register settings created by SCCM to point them to their SUP. I'm at a loss as to where to look now? It must be something simple! Any advice much appreciated. Thanks Kevin
  14. Hi all, So we have SCEP deployed to all clients in our environment. When looking at our servers status there is 24 at risk. When I dig in further they all have an "Endpoint Protection Remediation Status" of "Cleaned". Great! From my understanding, the server has had a threat and it has automatically been cleaned. My question is, how do I reset this status back to "Active clients protected with Endpoint Protection"? When we have a status of 24 at risk, it looks bad and they never seem to go back to a protected status. Thanks Kevin
  15. Thanks M13LU, Thats how I uninstalled it initially. It eventually started working after a week of failing. I'm still unsure of why it started working. The only thing I can think of that might have fixed it was installing a new Web Server Cert on the server that was not installing the client, even though the original cert was working. I'm not convinced though. Regards Kevin
  16. Hi all, I am having an issue with a DP, it was reporting as inactive in SCCM and because of this was not receiving software updates for the last couple of months. I tried to uninstall and reinstall the client on the inactive DP hoping it would fix the issue. However after uninstalling it I am unable to reinstall the client. The ccmsetup folder is created, but the client fails to install straight away. I get this repeating error; <![LOG[Checking the URL 'HTTPS://********:443/CCM_Client/ccmsetup.cab']LOG]!><time="14:59:23.634+00" date="01-06-2017" component="ccmsetup" context="" type="1" thread="1288" file="ccmsetup.cpp:10157"> <![LOG[PROPFIND 'HTTPS://********:443/CCM_Client']LOG]!><time="14:59:23.634+00" date="01-06-2017" component="ccmsetup" context="" type="1" thread="1288" file="httphelper.cpp:807"> <![LOG[Failed to correctly receive a WEBDAV HTTPS request.. (StatusCode at WinHttpQueryHeaders: 403)]LOG]!><time="14:59:24.041+00" date="01-06-2017" component="ccmsetup" context="" type="3" thread="1288" file="httphelper.cpp:1370"> <![LOG[Failed to check url HTTPS://********:443/CCM_Client/ccmsetup.cab. Error 0x80004005]LOG]!><time="14:59:24.041+00" date="01-06-2017" component="ccmsetup" context="" type="3" thread="1288" file="httphelper.cpp:1597"> <![LOG[Accessing the URL 'HTTPS://********:443/CCM_Client/ccmsetup.cab' failed with 80004005]LOG]!><time="14:59:24.041+00" date="01-06-2017" component="ccmsetup" context="" type="2" thread="1288" file="ccmsetup.cpp:10195"> <![LOG[Checking the URL 'HTTPS://********:443/CCM_Client/ccmsetup.cab']LOG]!><time="14:59:24.041+00" date="01-06-2017" component="ccmsetup" context="" type="1" thread="1288" file="ccmsetup.cpp:10157"> <![LOG[PROPFIND 'HTTPS://********:443/CCM_Client']LOG]!><time="14:59:24.041+00" date="01-06-2017" component="ccmsetup" context="" type="1" thread="1288" file="httphelper.cpp:807"> <![LOG[Failed to correctly receive a WEBDAV HTTPS request.. (StatusCode at WinHttpQueryHeaders: 403)]LOG]!><time="14:59:24.291+00" date="01-06-2017" component="ccmsetup" context="" type="3" thread="1288" file="httphelper.cpp:1370"> <![LOG[Failed to check url HTTPS://********:443/CCM_Client/ccmsetup.cab. Error 0x80004005]LOG]!><time="14:59:24.291+00" date="01-06-2017" component="ccmsetup" context="" type="3" thread="1288" file="httphelper.cpp:1597"> <![LOG[Accessing the URL 'HTTPS://********:443/CCM_Client/ccmsetup.cab' failed with 80004005]LOG]!><time="14:59:24.291+00" date="01-06-2017" component="ccmsetup" context="" type="2" thread="1288" file="ccmsetup.cpp:10195"> <![LOG[Checking the URL 'HTTPS://********:443/CCM_Client/ccmsetup.cab']LOG]!><time="14:59:24.291+00" date="01-06-2017" component="ccmsetup" context="" type="1" thread="1288" file="ccmsetup.cpp:10157"> <![LOG[PROPFIND 'HTTPS://********:443/CCM_Client']LOG]!><time="14:59:24.291+00" date="01-06-2017" component="ccmsetup" context="" type="1" thread="1288" file="httphelper.cpp:807"> <![LOG[Failed to correctly receive a WEBDAV HTTPS request.. (StatusCode at WinHttpQueryHeaders: 403)]LOG]!><time="14:59:24.525+00" date="01-06-2017" component="ccmsetup" context="" type="3" thread="1288" file="httphelper.cpp:1370"> <![LOG[Failed to check url HTTPS://********:443/CCM_Client/ccmsetup.cab. Error 0x80004005]LOG]!><time="14:59:24.525+00" date="01-06-2017" component="ccmsetup" context="" type="3" thread="1288" file="httphelper.cpp:1597"> <![LOG[Accessing the URL 'HTTPS://********:443/CCM_Client/ccmsetup.cab' failed with 80004005]LOG]!><time="14:59:24.525+00" date="01-06-2017" component="ccmsetup" context="" type="2" thread="1288" file="ccmsetup.cpp:10195"> <![LOG[Next retry in 10 minute(s)...]LOG]!><time="14:59:24.525+00" date="01-06-2017" component="ccmsetup" context="" type="0" thread="1288" file="ccmsetup.cpp:8835"> No other machines on our environment have this issue only this DP. I have checked certificates and all look good. The DP is reporting as fine in SCCM even without the client installed. I am having troubleshooting this. This particular DP used to be a Management Point and i suspect it went inactive around the time we uninstalled the MP role from this server. I have tried reinstalling the MP role, but this hasn't helped. Any help would be much appreciated. Thanks Kevin
  17. Hi Garth, What reports are you referring to? I had to create a custom report to get the machine last log. The user device affinity reports don't show the last log on, they show the "Last Modified Date". Kevin
  18. Hi All, I am hoping someone can help. I have been asked to investigate the possibility of creating a report for all windows user logins on computers within a certain collection. We want to be able to track the usage of machines, i.e. Criteria = COMPUTER01, who is logging in, when and for how long. We have device infinity enabled and automatic primary users enabled. However, any reports we run for logon stamps, are not giving us the information we need. On clients, the UserAffinity.log has all the information we need, but is there a way to get this into an automated report? The reason we want to use SCCM and not AD is that we already have all the information for the report in SCCM and combining multiple sources is causing a lot of inaccuracies. Thanks in advanced Kevin
  19. Hi all, I have been having the same issue for the last 6 months. We logged a Microsoft case and after much work got a resolution. Issue: Every time we tried to push an OS to a remote DP, within one hour it would fail. In the smsbkup.log I could see that there was a backup happening every hour, that happened at the same time the distribution failed. It was not related to the site maintenance or to do with any server back ups we had in place. Cause: Hyper-V replication. Our SCCM server is of course, virtual. It turns out Hyper-V replication is not supported with SCCM 2012, which I did not know. It uses the VSS_Writer which was stopping every hour. On our primary server, when we unchecked the "Volume Shadow Copy Service (VSS) snapshot frequency" which was set to hourly, this fixed the issue and we could distribute a large OS to the remote DP's. Hope this helps someone, this caused us a lot of work. Regards Kevin
  20. Hey all, I am struggling to find a solution to this, I am wanting create a query for what versions of 8.1 I have in my environment i.e. machines with Windows 8.1 and machines with Windows 8.1 update (KB2919355). Would anyone have such a report? Thanks Kevin
  21. Thanks Josh, This Query works perfectly! Much appreciated, Kevin
  22. Hi all, I am struggling to find a query that can do this for me. I am deploying software and I am wanting to add a query that will exclude any machines that haven't contacted AD within the last 45 days. Can anyone assist? Many thanks, Kevin
  23. Further more around the same time at 9.32 yesterday we have this error Message ID 1081 Site Component Manager could not install the SMS_SERVER_BOOTSTRAP_SELASCM11 service on site system "\\****" with the service logging on as account "". The operating system reported error 1115: A system shutdown is in progress. Possible cause: Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system. Configuration Manager cannot install component SMS_MP_CONTROL_MANAGER until the SMS_SERVER_BOOTSTRAP_SELASCM11 service can be installed. If this problem persists, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.
  24. Thanks Peter, I checked the mpMSI.log and the error I am getting is: --------------------------------- MSI (s) (AC:68) [09:31:59:230]: Note: 1: 1719 CustomAction SkipInstallCA returned actual error code 1601 (note this may not be 100% accurate if translation happened inside sandbox) MSI (s) (AC:68) [09:31:59:230]: Product: MSXML 6.0 Parser -- Error 1719. The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed. Contact your support personnel for assistance. Error 1719. The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed. Contact your support personnel for assistance. Action ended 09:31:59: SkipInstallCA. Return value 3. and MSI (s) (AC:EC) [09:32:02:392]: Product: ConfigMgr Management Point -- Error 1719. The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance. ------------------------------- So I repaired the windows installer and all looks fine with it. However when I try and install the MP, there is no record of it in the logs, only when it failed yesterday at 9.30am. The MP is present in "Servers and Site System Roles", but the role doesn't show in the Site Status under monitoring. I cant find any trace of the uninstall or reinstall of the MP anywhere, I am not sure what the underlying issue is or where to look. Kevin
  25. Hi, 2 days ago I received reports that clients were unable to registry with the CM management point. After reading up on it, it was recommended to reinstall the MP to see if this is a simple fix to the problem. So I uninstalled the MP and reinstalled it. I watched the MPSetup.log and it failed <10/29/14 09:31:58> ==================================================================== <10/29/14 09:31:58> SMSMP Setup Started.... <10/29/14 09:31:58> Parameters: C:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:SELASCM11 SMSMP 0 <10/29/14 09:31:58> Installing Pre Reqs for SMSMP <10/29/14 09:31:58> ======== Installing Pre Reqs for Role SMSMP ======== <10/29/14 09:31:58> Found 3 Pre Reqs for Role SMSMP <10/29/14 09:31:58> Pre Req MSXML60 found. <10/29/14 09:31:58> No versions of MSXML60 are installed. Would install new MSXML60. <10/29/14 09:31:58> Enabling MSI logging. msxml6_x64.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\msxml6_x64MSI.log <10/29/14 09:31:58> Installing C:\Program Files\Microsoft Configuration Manager\bin\x64\00000409\msxml6_x64.msi <10/29/14 09:31:59> msxml6_x64.msi exited with return code: 1603 <10/29/14 09:31:59> Backing up C:\Program Files\Microsoft Configuration Manager\logs\msxml6_x64MSI.log to C:\Program Files\Microsoft Configuration Manager\logs\msxml6_x64MSI.log.LastError <10/29/14 09:31:59> Pre Req CcmSetup found. <10/29/14 09:31:59> Installing pre-req using command line "C:\Program Files\Microsoft Configuration Manager\client\ccmsetup.exe" /UpgradeWithServer:mp <10/29/14 09:32:01> Pre-req installer "C:\Program Files\Microsoft Configuration Manager\client\ccmsetup.exe" /UpgradeWithServer:mp finished with exit code 0 <10/29/14 09:32:01> Pre Req SqlNativeClient found. <10/29/14 09:32:01> SqlNativeClient already installed (Product Code: {49D665A2-4C2A-476E-9AB8-FCC425F526FC}). Would not install again. <10/29/14 09:32:01> Pre Req SqlNativeClient is already installed. Skipping it. <10/29/14 09:32:01> ======== Completed Installation of Pre Reqs for Role SMSMP ======== <10/29/14 09:32:01> Installing the SMSMP <10/29/14 09:32:01> Passed OS version check. <10/29/14 09:32:01> IIS Service is installed. <10/29/14 09:32:01> No versions of SMSMP are installed. Installing new SMSMP. <10/29/14 09:32:01> Enabling MSI logging. mp.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log <10/29/14 09:32:01> Installing C:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi CCMINSTALLDIR="C:\Program Files\SMS_CCM" CCMSERVERDATAROOT="C:\Program Files\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1 <10/29/14 09:32:02> mp.msi exited with return code: 1603 <10/29/14 09:32:02> Backing up C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError <10/29/14 09:32:02> Fatal MSI Error - mp.msi could not be installed. <10/29/14 09:32:02> ~RoleSetup(). So I uninstalled the MP again, restarted the server and reinstalled the MP. Now the MPSetup.log & mpMSI.log logs show NO record of me uninstalling or restarting it now. No matter how many times I try. The MP shows as installed in the Site System Roles, but is not present in the Site Status. I installed the role as a user with full admin rights. Has anyone experienced this issue?
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.