Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

  • Days Won


dinci5 last won the day on November 9 2017

dinci5 had the most liked content!

Community Reputation

7 Neutral

About dinci5

  • Rank
    Advanced Member

Recent Profile Visitors

1,525 profile views
  1. Because the Icon table is already present in your MSI. You even selected it on your left side.
  2. Hi,I have upgraded my lab to 1810 recently. And I think something is broken.The lab is setup in Hyper-V and used to work fine before.Ever since I've upgraded, my deployments are not working.A couple of errors from smsts.log:"Network access account credentials are not supplied or invalid.""Failed to get client identity (80004005)""failed to request for client""SyncTimeWithMP() failed. 80004005.""Failed to get time information from MP: http://LAB-CFG.Domain.com."Now, I've seen this error before in our Live environment and back then it was an issue with the date and time on the clients.I solved t
  3. I don't like that method. I just use the recommended driver method.
  4. You could remove the content from your DP's and then re-distribute again. Properties of the Application > Content Locations > Select one by one and Delete. This should do the trick.
  5. Don't use the shutdown tool. Use Powershell App Deploy Toolkit instead. The shutdown tool might be seen as malicious by some AV There is even a built in function in the toolkit called "Get-PendingReboot" which you can use to check whether there is actually a reboot pending an then use a notification popup to notify users or force a shutdown.
  6. Hi, How do you guys manage the Surface Pro drivers? We have a couple hundred Surface Pro 3 and Surface Pro 4 devices. Now that I want to deploy W10 1709 I had a hard time figuring out which drivers to download for this version due to the stupid and extremely confusing versioning of these driver packages. For instance, the latest driver pack for the SP 4 is called "SurfacePro4_Win10_15063_1704201_0.zip". So by looking at the filename you would guess that it's only for W10 1703. Turns out, according to this blog post, it states that the driver pack with that name is for W10 17
  7. Yes yes, that's what I do. I change the key to the KMS key and I don't get the OEM issue anymore. Now I'm still struggling with the issue where the TS doesn't complete successfully and CM Client is messed up. The Windows upgrade is successful. It's also reflected in the Setupact.log It all starts here:
  8. I'm starting to hate SCCM. This product has so many bugs it really isn't fun anymore. Now all my upgrades hang at setupcomplete.cmd until it times out. After OS starts the CM client is stuck in Provisioning Mode. The OS is upgraded though and it works fine. But the TS never completes successfully. Only thing I see in smsts is this: Succeeded loading resource DLL 'C:\WINDOWS\CCM\1033\TSRES.DLL' TSManager 11/14/2017 10:28:08 AM 5952 (0x1740) Failed to create an instance of COM progress UI object. Error code 0x80040154 TSManager 11/14/2017 10:28:08 AM 5952 (0x1740) Timed
  9. Upgrading from Pro. I'll have to use MAK keys then because those remote users rarely connect to our network so devices won't stay activated forever. That's why the OEM keys were ok for us. We don't use any features from from W10 Enterprise anyway.
  10. From 1607 and 1703. I think I figured out what was going on. In Setupact.log I saw this line: "Client OS edition and OEM license detected and no enterprise edition detected, will not run SetupComplete.cmd" So the SetupComplete.cmd script didn't run which caused the TS to stop and the CM client to remain in Provisioning Mode. Due to the specific nature of the client they have devices with OEM licenses as well. This is because many employees work in remote locations (Africa, South America, Asia, etc...) and they purchase devices locally with OEM licenses. Those are then joi
  11. Ho do you deploy the application? Did you wrap it in a script? VBS, bat, PS? If so, you can easily append that command in the script.
  12. Hi, I'm testing an Upgrade TS to Win 10 1709. I tested 4 devices now. On devices, all was working fine. Update was successful. On other two devices, the OS upgrade was successful, but after the OS boots again the TS doesn't complete successfully. I have two batch files in the Post-Processing group which are not executed. One of them just creates a txt file so I know it did run actually. In Software Center, the TS has status "Installing..." and it keeps spinning like that for hours. The smsts.log files is also not updated anymore after the last reboot. So the Se
  13. Here is a tip how to add an icon to 7Zip (or any other MSI that doesn't contain an icon): Download and install Orca. Right click on the 7Zip MSI installed > Edit with Orca in Orca go to Transform > New Transform Hit CTRL+T to add a new table. (or right click in the Table pane > Add Tables) Select Icon from the list. Click the Icon table and add a new row: Right click > Add Row Enter Row Name; Data: browse to a file that contains the Icon. I usually just browse to the application EXE of the installed application as it contains an icon bu
  14. Is this only an issue if upgrading from 1610? I'm planning an upgrade from 1606 to 1702; This topic just scared the shit out of me. I wouldn't know what to do if it fails.
  • Create New...