Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

fj40ratt's Achievements


Newbie (1/14)

  • Conversation Starter Rare
  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges



  1. I've been trying to remove this update on a test device for the last 3 days using a task sequence with the command line wusa.exe /uninstall /kb:5005565 /quiet /norestart or inserting the .msu file. Neither attempt will work. I have been successful in the past removing troublesome Windows updates using this method but this one is driving me crazy. Has anyone else had to remove this particular update and been successful using SCCM? Thanks.
  2. I've tried both creating a TS from scratch and copying from another TS. Neither has been successful. I even tried just making it a simple 8 character password containing nothing but letters with no luck. Crazy thing is that when I verify the account and password connection to the OU within the TS it verifies just fine and that same account and password will manually join a device to the domain successfully. Might be time to get Microsoft involved.
  3. Jumped the gun. The new password works for one of my task sequences but not for any of my other TS's including any new from scratch TS's. This is crazy.
  4. I seem to be running into this more often as of late. I've created a basic OSD task sequence but when I attempt to deploy it the collection I wish to direct it to, it does not appear in my list. I know it is there because I have deployed other OSD task sequences to the same collection previously without issue and I can see the collection. I also run into this when I create a new device collection and try to deploy an existing TS to it. Thoughts? Thanks.
  5. Update: New 15 character password that utilized all 4 of the complexity rules in AD worked successfully. The previous attempts that were failing were only matching 3 of the 4 requirements which should have still worked since the password rule states you must have at least 3 of the 4. Really odd. Thanks for the input and willingness to help test everyone.
  6. Will try to get that info to you sometime today or tomorrow. Attempting another password change today.
  7. The computer name has 8 characters. I won't be able to get a smsts.log file to you until Monday. I have people imaging this week so I can't test a password change until they are finished.
  8. It was not integrated. Thanks Niall. Good luck. I'm trying to do more testing this week myself.
  9. Update: A 15 character pwd with nothing but upper and lowercase letters and numbers caused the device to not join the domain. Also double checked to make sure the password was meeting the domain complexity requirements and it is. This one is really odd.
  10. Thanks pzov, appreciate the input. I've run up against that type of issue with other systems in the past as well. I believe this is the first time I've attempted that complex of a password with SCCM. You would like to believe that Microsoft would make sure their complexity requirements were standard across the company. If Active Directory accepts that long of a password from a user, their own systems should allow it when they talk to each other. lol I will test with a long password avoiding any special characters and update here with the results.
  11. Version 2002 Console Version: 5.2002.1083.2000 Site Verison: 5.0.8968.1000
  12. Always appreciate your advice Niall. I have. I'm actually using it in the Apply Network Settings task. I don't have a Join Domain section in the TS anywhere. Another test I just ran is I added an additional character to the original password to create a new password of 9 characters. Old password that worked prior was only 8 characters. I then changed the pwd in the TS to the new 9 character pwd and it still works as intended. When my AD admin changed the password earlier on the domain join account, he changed it to a 20 character password and that is the TS would fail to join the device to the domain. Is there a password length restriction that anyone is aware of?
  13. Good morning SCCM brains. Here is one that has me about ready to trade mine in for a beer. Last week our AD admin changed the password for the account that does our AD joins during task sequence image deployments. I have entered the new password in the TS, verified it's access to the OU in AD successfully, and can use the new password to manually join a device to the domain without issue. Unfortunately when the TS now runs the device fails to join the domain. I've looked in the netsetup.log, setuperr.log and setupact.log to verify the correct account is present which it is but the error indicates it is still a bad username or password. I had our AD admin change the password back to the original password in AD and imaging works perfectly with the device joining the domain as expected. Is there somewhere else in SCCM I should be looking for that password to be changed? Thanks in advance.
  14. I'm trying to deploy an application that has multiple dependencies. One of the dependencies is Visual C. The application deployment fails because it states that Visual C already exists and it must be uninstalled through control panel for the deployment to succeed. Is there a way during application deployment to bypass a dependency if it already exists on the target computer? Thanks in advance.
  15. Thanks for the reply Niall. I totally understand not using the capture method but I don't know of another way get a single WIM file to the company that will be doing our imaging of new machines and still maintain the multiple partitions needed for BitLocker. These machines need to be as close to end user ready when they arrive here. The goal is to eliminate as much customization work as possible for our field techs. It's unfortunate that SCCM lets you create the multiple partitions during the TS but it doesn't provide a way to then capture the machine exactly as it is once you have it customized just for situations like this unless I'm missing something.
  • Create New...