Jump to content


VinnieBaz

Established Members
 View Profile  See their activity

  • Posts

    20

  • Joined

  • Last visited

 Content Type 

Everything posted by VinnieBaz

  1. VinnieBaz
    Hi, Did you manage to solve this?
  2. VinnieBaz
    ooh wow, totally missed that.. Thanks..
  3. VinnieBaz
    Hi Niall, I´m working on adding the new version of your great tool and noticed a reg value that looks out of Place. In the upgrade.hta, line 352 "//var key = "HKCU\\Software\\windowsnoob\\UpgradeComputer";" Shouldn´t this line also be something like " + CompanyName + "? Kind regards
  4. VinnieBaz
    Thansk! No point of troubleshooting this then
  5. VinnieBaz
    Indeed I am.
  6. VinnieBaz
    We had some old DHCP options still present on the Scopes even though we are using IP-Helper, removing those got us running on one VLAN.
  7. VinnieBaz
    Any new info on this? I was testing this out earlier and got it to work on our "primary" VLAN. We are using IP-helper and from what I can tell it´s configured the same way on all VLANs. Using WDS works fine on any VLAN byt SCCMPxe doesnt ?
  8. VinnieBaz
    Hi there and welcome. You can install software in multiple ways, I myself is also somewhat new to SCCM and is using what I think is the easiet way. I assume you already have the applcations added in SCCM and if so, you can just edit the task sequence you use for OS Deployment and add the applicatons. Note that if you want to install an application that is not deployed you must allow that by checking the box in the third attached imaged. Hope this is somewhat helpful
  9. VinnieBaz
    Nothing that pops up right away.. I guess you could try to make a new export from a computer were you set Adob as default PDF reader and then manually import it on a test client to see if it works.
  10. VinnieBaz
    We had that same issue but I found out that in our case it was caused by using old export files. The applicationstrings and what not is updated with every Win 10 version, so if you have exported the default App association file from a client running 1703 you can encounter the behaviour you explain when importing it to a client running a diffrent version. Thumbrule is to make a new export for every Windows version your are running, its been working fine for us after we started doing that.
  11. VinnieBaz
    Never tried using the GPO method my self. Is it only Adobe that fails or are you trying to change default apps for any other app?
  12. VinnieBaz
    So how are you trying to accomplish this? Have you done the export from a reference machine running 1709?
  13. VinnieBaz
    What method are you using while applying this? I've been using this with OSD since Win 10 1511 with no issues at.. Since I set default assoc for several apps its a good idea to do the export from a reference client running the same version you want to apply it on.
  14. VinnieBaz
    We are running 6.3.8450.1000, however I do belive it's working now.. While addding the steps to my task I was following your guide in the .docx you have published here. In that guide it says But in the guide here in the forum it says So i replaced the ServiceUI.exe x64 with the x86 and that seem to have fixed it..I also removed the windowhide.exe, will I need it? Anyways, thanks for helping me out and keep up the good work!
  15. VinnieBaz
    No, the script is downloaded from your link, unzipped and pasted in the package folder.. I re-attach it here. I´m trying to do an inplace upgrade for 1709 x64, so i picked the ServiceUI and WindowHide from the x64 folder. WindowsSetupCompatibilityScanResults.zip
  16. VinnieBaz
    Hmm, wrong version of ServiceUI sounds most likely then, the script is copied from this thread without and tweaks so shouldn't be anything wrong with it.. Thanks for your time, I'll take a look at the ServiceUI file and let you know how it goes Btw, what Service UI should i use? I Copied mine from the x64 folder in the Deploymentshare\Tools directory, isnt that the one i need?
  17. VinnieBaz
    I´m very well aware of that, but why is the WindowsSetupCompatibilityScanResults.ps1 failing to run? I want the pop-up notification, I want the Logs to be moved to my server.. Like i said earlier, the log is from a virtual machine with only 1 GB RAM and the "Check Readniess" step disabled..
  18. VinnieBaz
    Here you go! This is from the client with only 1 GB RAM and wtih "Check Readniess" disabled in the TS. Client1-smsts.log
  19. VinnieBaz
    This thing keeps failing me.. is there anything needed to be customized in the WindowsSetupCompatibilityScanResults.ps1 for this to work? I'm running two VM`s, one with 1 GB RAM to test this out, the other with enough RAM to pass the scan.. However both of them "fails".. Looking in the SMSTS.LOG on the VM with low RAM i can see the exit code: Windows setup in 'scanOnly' mode returned exit code hexadecimal 0xC1900200 ( decimal 3247440384) . Failing task sequence step. However, in the WindowsSetupCompatScan.log I get the following: Starting Windows Setup compatibility scan results script The following hardware was detected: Microsoft Corporation Virtual Machine The original decimal returncode was: The converted HEX returncode is: 0 Found value at 0 0 On the VM with enough RAM, the SMSTS.log returns exit code 0xC1900210 and passes the test, however in the WindowsSetupCompactScan.log I get the same result as from the machine failing Starting Windows Setup compatibility scan results script The following hardware was detected: Microsoft Corporation Virtual Machine The original decimal returncode was: The converted HEX returncode is: 0 Found value at 0 0 So both VM´s gets the "Sorry, but this computer isn't ready to be upgraded right now. Please inform your IT department that the result of the Windows Setup compatibility scan was: No compatibility issues.('0') What am I missing?
  20. VinnieBaz
    Hello! My upgrade TS fails with following error after scan has run.. Process completed with exit code 4294967295 Failed to run the action: Process Windows Setup Compatibility Results. Unknown error (Error: FFFFFFFF; Source: Unknown) I did some tests after the task failed and noticed that I was able to get the notification pop-up if I changed this path: %windir%\sysnative\WindowsPowerShell\v1.0\powershell.exe to %systemroot%\syswow64\WindowsPowerShell\v1.0\powershell.exe Is the first path wrong or is it supposed to work?
×
×
  • 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.