- #SKETCHUP PRO 2017 THUMBSUP.DLL INSTALL#
- #SKETCHUP PRO 2017 THUMBSUP.DLL PRO#
- #SKETCHUP PRO 2017 THUMBSUP.DLL LICENSE#
- #SKETCHUP PRO 2017 THUMBSUP.DLL WINDOWS#
#SKETCHUP PRO 2017 THUMBSUP.DLL WINDOWS#
So we’re going to move all of our deployed computers throughout the district to Windows 10. Like with all good projects, we need to figure out what the hell we’re trying to do in the first place before leaping into actually doing it. Using WindEducation, I applied a number of customizations, drawn from several expert sources and cobbled together into my own Frankenstein’s-Monster of a deployment, with SCCM 1702. Naturally, both could be combined into a single batch file, but I kept them separate so that I could activate & deactivate either in my task sequence while I’m still testing.
#SKETCHUP PRO 2017 THUMBSUP.DLL PRO#
In my source folder, I have four files: the Sketchup MSI installer itself, my activation_info.txt, cleanuplinks.cmd, and .ĭel "C:\users\public\Desktop\Layout 2017.lnk"ĭel "C:\users\public\Desktop\SketchUp 2017.lnk"ĭel "C:\users\public\Desktop\Style Builder 2017.lnk"Ĭopy "\\systemcenter\sources\Apps\SketchUp Pro 2017\Files\activation_info.txt" "c:\programdata\sketchup\sketchup 2017"
#SKETCHUP PRO 2017 THUMBSUP.DLL LICENSE#
CMD files to copy the volume license file and to clean the desktop of the shortcuts that Sketchup created. I grabbed the stand-alone installer for VC++ 2015, packaged that up, then applied it to my task sequence. FAILURE! I forget the exact error message, but it would fail:įor our friendly neighborhood search engine crawlers, the text of the error is: Module C:\Program Files\SketchUp\SketchUp 2017\ThumbsUp.dll failed to register.
#SKETCHUP PRO 2017 THUMBSUP.DLL INSTALL#
I wiped the machine and tried to install Sketchup by itself. I manually installed VC++ 2015, then installed Sketchup.
![sketchup pro 2017 thumbsup.dll sketchup pro 2017 thumbsup.dll](https://m.aiweibk.com/wp-content/uploads/2021/09/2021091211153276.jpg)
My vanilla Win10 install has 2013 installed. NET 4.7 anyway.īut they also mentioned needing to install the Visual C++ 2015 Redistributable. That sounded strange to me, especially since attempting to install 4.5.2 on an updated and patched Win10 introduced even more work than I wanted to put in.
![sketchup pro 2017 thumbsup.dll sketchup pro 2017 thumbsup.dll](https://aws1.discourse-cdn.com/sketchup/original/3X/6/7/6731defe0182c37488ff2b01c1a44368ae953af8.png)
NET Framework 4.5.2, and seemed to imply that 4.5.2 was the only version that it supported. Sketchup’s support site mentioned that 2017 requires. But no matter what I tried, 2017 would fail during a task sequence with the dreaded 0x80004005. 2015 seemed to deploy much more smoothly, despite having to implement a few kludgy workarounds. After correcting that, my Lat 7470s partitioned, formatted, and applied the OS correctly.īut how in the hell did that get changed in the first place?įor the past few months, I’ve been struggling to deploy Sketchup 2017 with SCCM. The variable “_SMSTSBootUEFI” had somehow changed to “_SMSTSBookUEFI.”Īnd since I copy/paste tasks from sequence to sequence, I had inadvertently copied this error to all of my Win 10 task sequences. I looked at my task sequence variables, because everything else looked fine. Why? It had to be that step, because the NUCs, which are on legacy boot, partition normally as BIOS. I then noticed that the step where the TS should be formatting my drive to UEFI was not actually starting.
![sketchup pro 2017 thumbsup.dll sketchup pro 2017 thumbsup.dll](https://aws1.discourse-cdn.com/sketchup/original/3X/e/7/e72ed272b97595f3638768c7715fc608401a932b.png)
Check your task sequence to ensure this drive is correct and that it is being createdThe parameter is incorrect. Check your task sequence to ensure this drive is correct and that it is being createdThe requested target could not be resolved to a valid volume on this computer. The requested target could not be resolved to a valid volume on this computer. There are no more volumes available for use. The task sequence on the Lats go really quickly to Applying Operating System where it failed. The same task sequences, so it wasn’t the software. Yet they were fine on my testbed Intel NUCs. This past week, my Win10 task sequences were failing on the Latitude E7470s.