Jump to content


Joe13

Established Members
  • Posts

    75
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Joe13

  1. Sure no problem, attached my config previously.
  2. Would you like to install the driver or copy it to a directory for later? I copy some drivers for various printers to a directory during my TS so that they are readily available for our support guys to install IF required.
  3. I managed to solve this the wrong way by opening the GPO for updates to check for other products and from other sources. It refused to use my SCCM server even though those sources only specify configuration manager.
  4. Yes sir, all services run with local system. The accounts being locked out are domain users.
  5. Hi all, I need some help with figuring out why AD accounts are getting locked out. I did some extensive googling but cannot trace it. Hybrid environment with AAD. On-prem OWA disabled to the outside. All email accounts in O365. I traced it this way On my DC’s, lockout source is exchange server. On my exchange server Caller Process Name: C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeFrontendTransport.exe I cannot find any source in the iis log files. If I disable the MSExchangeFrontendTransport.exe service the accounts don’t lock out. I’m pulling my hair out with this, what else can I do to properly trace and find out what the cause is? AD acc lockout.txt Exchange acc lockout.txt
  6. Hi, I have a new issue in SCSM 2016. I have no reports. I checked SSRS and my account has access, on the console, when I click on reports it's just empty. I upgraded to 2019 and then to 2022 but it stays the same. Updated SQL to their latest CU's too. Any ideas what else to try?
  7. One of the issues I found. The operating system reported error 615: The password provided is too short to meet the policy of your user account. Please choose a longer password.
  8. Hi all, I recently noticed that during OSD, only 1 or 2 steps are displayed during the process. The rest "hides" behind the "Just a moment" Windows loading screen. So I can't open F8 to export the log file, I'm experiencing issues with software that won't install. When the TS is deployed, "Shows steps" is selected. Any ideas?
  9. Don't we have any AD masters here to assist?
  10. Hi all, I have a serious problem with a password policy. When I view the status it indicates that the password can be kept for ages, yet my enforced policy dictates 60 days. The account does expire. User account control attribute is on 512. It's not all the same for everyone on AD. I tried to narrow it down to a policy but cannot find the issue.
  11. Hi all, My endpoint protection clients aren't updating. I noticed it happening this last month. Most clients are 2 to 7 days outdated. They are receiving the correct policy. I'm on SCCM 2203 as of today. Attached 2 images of log files from different clients.
  12. Yes sir, I checked these first. I removed the site system role and added it again. It's busy downloading now and I don't see any errors in my log, for now. I will report back.
  13. Hi everyone, please help me before I crack my scull. I'm unable to update my SCCM server, I'm not sure what happened. I never had this issue. I get the following in the log file, I see the following error/IP but have no idea where to change it, 192.168.5.42:8080 ERROR: Failed to download Admin UI content payload with exception: Unable to connect to the remote server SMS_DMP_DOWNLOADER 2022/06/06 12:18:51 PM 11836 (0x2E3C) Failed to call AdminUIContentDownload. error = Error -2146233079 SMS_DMP_DOWNLOADER 2022/06/06 12:18:51 PM 11836 (0x2E3C) AdminUI Content Download thread is exiting... SMS_DMP_DOWNLOADER 2022/06/06 12:18:51 PM 11836 (0x2E3C) ERROR: GetSccmConnectedServiceUrl Exception System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.5.42:8080~~ at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)~~ at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)~~ --- End of inner exception stack trace ---~~ at System.Net.HttpWebRequest.GetResponse()~~ at Microsoft.ConfigurationManager.DmpConnector.Connector.SCCMConnectorUtility.GetSccmConnectedServiceUrl(IWebProxy prx) SMS_DMP_DOWNLOADER 2022/06/06 12:18:51 PM 10860 (0x2A6C) There is no sccmConnected service reachable SMS_DMP_DOWNLOADER 2022/06/06 12:18:51 PM 10860 (0x2A6C) Generating state message: 1 for package 00000000-0000-0000-0000-000000000000 SMS_DMP_DOWNLOADER 2022/06/06 12:18:51 PM 10860 (0x2A6C) Write the state message in C:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\high\___CMUfobzsk4w.SMX SMS_DMP_DOWNLOADER 2022/06/06 12:18:51 PM 10860 (0x2A6C) Successfully Dropped the state message 1 SMS_DMP_DOWNLOADER 2022/06/06 12:18:51 PM 10860 (0x2A6C) Download manifest.cab SMS_DMP_DOWNLOADER 2022/06/06 12:18:51 PM 10860 (0x2A6C) WARNING: Failed to download easy setup payload with exception: Unable to connect to the remote server SMS_DMP_DOWNLOADER 2022/06/06 12:19:12 PM 10860 (0x2A6C) WARNING: Retry in the next polling cycle SMS_DMP_DOWNLOADER 2022/06/06 12:19:12 PM 10860 (0x2A6C) Download QFE payloads SMS_DMP_DOWNLOADER 2022/06/06 12:19:12 PM 10860 (0x2A6C)
  14. I fixed it for now by changing my network adaptor on VMWare from VMXNET3 to E1000E. It now owrks without issues.
  15. Back to square one. It now takes 30minutes just to download the .wim What logs files and events can I refer to for troubleshooting? I cleared required PXE deployments. I updated the distribution points, default boot images and mine. SMSPXE.txt
  16. I think I solved it. I made the RamDiskTFTPBlockSize lower than normal...
  17. Hi gents. I'm pulling my hair out, whole of last week and this week I'm using OSD to deploy PC's for a new contract. Few hours ago all stopped working, any PC or laptop, intel, hp, lenovo. All fail with this error. Nothing on my environment changed. Some research takes me to the March 2019 CU update. It is not installed on my server. Both these registry keys were set back to default with no difference on the outcome. RamDiskTFTPBlockSize RamDiskTFTPWindowSize I also tried this suggestion: https://andys-tech.blog/2019/03/wds-required-device-isnt-connected-or-cant-be-accessed/ The error reads: Status: 0xc0000001 Info: A required device isn't connected or can't be accessed.
  18. Hi all, I need some help please. I would like to change the default HP logo, the one during boot. According to this article I need to have a logo file and copy it to their partition and it should work. https://support.hp.com/za-en/document/c01646879 In my TS I created this additional partition - see attached. 1. Is this correct? 2. How do I create a sub folder and copy my logo file to this hidden partition? 3. Is my layout correct, refer to attached "UEFI Layout"?
  19. I would also like to know how to do this during OSD. If I deploy this using GPO the standard users are prompted to enable UAC to run any built in app, like calculator.
  20. I did do permissions on the specific OU. Will be trying this - https://eddiejackson.net/wp/?p=16416 Referring to this unanswered post - The computer already exists in AD, how can I handle this then.
  21. Also found this: 09/06/2019 12:55:06:378 NetpGetComputerObjectDn: Passed OU doesn't match in size cracked DN: 120 106 09/06/2019 12:55:06:378 NetpCreateComputerObjectInDs: NetpGetComputerObjectDn failed: 0x50 09/06/2019 12:55:06:378 NetpProvisionComputerAccount: LDAP creation failed: 0x8b0 09/06/2019 12:55:06:378 NetpProvisionComputerAccount: Cannot retry downlevel, specifying OU is not supported
×
×
  • 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.