Jump to content


xerxes2985

Established Members
  • Content Count

    169
  • Joined

  • Last visited

  • Days Won

    4

xerxes2985 last won the day on July 25

xerxes2985 had the most liked content!

Community Reputation

4 Neutral

About xerxes2985

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. So far, everything I've checked on this list is valid. All permissions are in place, wmi permissions correct. This computer has network connectivity to the SMS Provider computer. • Your user account has Remote Activation permission on the Configuration Manager site server and the SMS Provider computer. • The Configuration Manager console version is supported by the site server. • You are assigned to at least one role-based administration security role. • You have the following WMI permissions to the Root\SMS and Root\SMS\site_<site code> namespaces: Execute Methods, Provider Write, Enable Account, and Remote Enable. Yet, SMSAdminUI.log shows the following: 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) at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)\r\n [5, PID:1184][09/27/2019 11:25:06] :Insufficient privilege to connect, error: 'Access is denied. '\r\nSystem.UnauthorizedAccessException\r\nAccess is denied. \r\n at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) 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) at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)\r\n Thanks for any help you can provide,
  2. Checked, the account is a member of the group called SMS Admins that has access to run the console. Should I remove / re-add the account from there, as well as in the SCCM console?
  3. Hi all. I've been connecting just fine using an account that is a full administrator on the site server. Now, unless I run the program as an administrator, and use a different "full administrator" account, I get the following error. Please guide me in resolve (what logs etc) The Configuration Manager console cannot connect to the Configuration Manager site database. Verify the following: • This computer has network connectivity to the SMS Provider computer. • Your user account has Remote Activation permission on the Configuration Manager site server and the SMS Provider computer. • The Configuration Manager console version is supported by the site server. • You are assigned to at least one role-based administration security role. • You have the following WMI permissions to the Root\SMS and Root\SMS\site_<site code> namespaces: Execute Methods, Provider Write, Enable Account, and Remote Enable.
  4. Hello all. I've run into a bit of an odd issue with a defaultuser0 account being created, as well as an "account unknown" showing up in User Profiles. I am able to log in with a domain account, as well as a local account, but one side effect of these two "accounts" is that the "Desktop" shortcut under "Quick Access" is stuck to "C:\Users\Default\Desktop" regardless whether a domain or local account logs on the computer. Is there some step I can do to prevent this "defaultuser0" and account unknown from being created, or any way to purge these two accounts during OSD? I manually can remove Account Unknown, delete C:\Users\Default, re-pin the "Desktop" to quick access, and it functions fine. Additional info: Used build and capture process on a base install.wim, did no configuration changes, so essentially a vanilla image, but not just using install.wim.
  5. On your Dell BIOS are you checking all the boxes next to the Enable PPI options on TPM?
  6. Imaging using a working image, complete with all the requirements for NVMe drives (Intel RSTe drivers, etc). The TS is just a basic install OS, with nothing additional. Once the image applies, and it goes to reboot into Windows, a box comes up saying Windows Setup could not configure on this hardware. Computer is a Dell Precision T5820 with a 512mb PCI-E NVMe drive Any thoughts, ideas?
  7. Primarily the remaining computers I am upgrading are Windows 7, so I'd like to hit them all with Windows 10 1703, then right after upgrade them to 1903. I've got individual collections for both 7, and 1703. Was hoping/trying to accomplish a one-two punch to upgrade, then upgrade.
  8. Is it safe to chain an OS upgrade Task Sequence? For example, I've finally been able to upgrade Windows 7 Enterprise SP1 to Windows 10 Enterprise 1703, then once that upgrade is complete, I want it to immediately upgrade from 1703 - 1903. Will it work like this? Or do I need to create some sort of variable, etc. Thanks!
  9. You should be using the Acrobat Customization Wizard, when you open AcroPro.MSI to create a new transform, you'll see the following. Place the serial number in there, choosing the "grant offline exception & Disable registration"
  10. That's what I'm going to try. I was hoping to skip having to upgrade to upgrade to upgrade.. but it may be the solution
  11. Unfortunately, the program fails to run successfully on Windows 7. On the MS page, it specifies the The destination OS must be Windows 10.
  12. Good morning, Over the past few weeks, I've been attempting to upgrade a Windows 7 Enterprise SP1 (x64) client to Windows 10 1903 CBB (SAC I think its called now) x64. Each time, it gets through the process to about 78%, and then rolls back the installation. I've tried using an OS Upgrade package, I've tried manually using an ISO, even creating a DVD to complete the upgrade, and they all come back with the same errors. I've attached setuperr.log (from the $WINDOWS.~BT folder). What am I missing that is causing this to fail? setuperr.log
  13. Whether I do or don't, it still fails with the same information.
  14. I'm using the "upgrade operating system task sequence", using the full media for 1903 x64 Semi Annual Channel (formerly CBB I believe). My attempt is to go from 1607 LTSB to 1903 CBB. I have an OSDSetupAdditionalUpgradeOptions specified, as the entry for Product Key didn't seem to put the "/pkey" into the command line. From smsts.log on a box that was affected, this is the resulting command it is running. Shortly after it fails with the "unknown error 0x80004005", I check setupact.log and setuperr.log and it shows the the following errors: One thing that sticks out is "Selected install choice is not available". ![LOG[Command line of Windows Setup upgrade: '"C:\_SMSTaskSequence\Packages\LIB001F8\SETUP.EXE" /ImageIndex 3 /auto Upgrade /quiet /noreboot /postoobe "C:\Windows\SMSTSPostUpgrade\SetupComplete.cmd" /postrollback "C:\Windows\SMSTSPostUpgrade\SetupRollback.cmd" /DynamicUpdate Disable /compat IgnoreWarning /pkey NPPR9-FWDCX-D2C8J-H872K-2YT43']LOG]! If I manually run setup.exe /pkey NPPR9-FWDCX-D2C8J-H872K-2YT43 from the mounted ISO, it upgrades from 1607 LTSB to 1903 CBB just fine. Any suggestions?
×
×
  • Create New...