Starting in version 2103, the ConfigurationManager PowerShell module requires Microsoft.
If the device doesn't already have it, the console setup doesn't install this prerequisite. If you install the console on other devices, make sure to update. NET Framework version 4.6.2, but version 4.8 is recommended. Starting in version 2107, the console requires Microsoft. You have Read permissions to the location of the console installation files.
You have local Administrator rights on the target computer for the console. Supported OS versions for Configuration Manager consoles To install the console separate from site server installation, run the standalone installer. The Configuration Manager console is always installed on the site server for the CAS or a primary site. You can't connect a Configuration Manager console to a secondary site. Each Configuration Manager console can connect to a central administration site (CAS) or to a primary site. Applies to: Configuration Manager (current branch)Īdministrators use the Configuration Manager console to manage the Configuration Manager environment.
2147944122 – The RPC server is unavailable. 2147942405 – Access is Denied (Firewall rule? / MacAfee-HIPS?). 2147749908 – Initialization failure – Source: Windows Management (WMI). 2147749904 – Invalid class – Source: Windows Management (WMI). 2147749890 – not found – Source: Windows Management (WMI) – try repair WMI. 2147749889 – Generic WMI failure (Broken WMI). 1450 – Insufficient system resources exist to complete the requested service. (NBTSTAT -a reverse lookup, duplicate IP address) 1396 – Logon Failure: The target account name is incorrect. 1208 – An extended error has occurred. Please try retyping the path or contact your network administrator. 1203 – The network path was either typed incorrectly, does not exist, or the network provider is not currently available. 1130 – Not enough server storage is available to process this command. 1068 – The dependency service or group failed to start. 1053 – The service did not respond to the start or control request in a timely fashion. 86 – network password is not correct? Machine Name resolved name. 64 – The specified network name is no longer available. 58 – The specified server cannot perform The requested operation. 53 – Unable to locate – – cannot connect to admin$ – Computer Browser not started – add File/print sharing to Exceptions in Firewall – turn file and print on. Make sure there is not a duplicate name in DNS and that 2 machines don’t have the same IP in DNS. 
52 – You were not connected because a duplicate name exists on the network.2 – The system cannot find the file specified.
0 kommentar(er)
