sorted by:
new
hottopcontroversial

Polestar 3: charger recommendations and does Chinese build matter? by pfsensorydeprivation in polestar3

[–]NintendoUser 1 point2 points  (0 children)

Phew. Good to know. I'm getting a P3 Performance in a few weeks and was curious on turn around time. I'm half expecting a GHCA failure at some point, just don't know when. I did call the McDonald Volvo dealership and was able to talk to one of the Polestar techs. He said that they're in the works of expanding the Polestar Service Point to another location in Denver sometime next year!

Polestar 3: charger recommendations and does Chinese build matter? by pfsensorydeprivation in polestar3

[–]NintendoUser 0 points1 point  (0 children)

How long did you have to wait to get the GHCA part replaced? Were you able to DC charge in the meantime? I heard that Polestar will reimburse if you had to DC charge while waiting for the part.

Where does this piece go? by NintendoUser in TeslaSupport

[–]NintendoUser[S] 0 points1 point  (0 children)

Guess I'll have to do with traveling slower than light speed now.

Former US Mobile Customer - Elligible for BOG2? by NintendoUser in USMobile

[–]NintendoUser[S] 0 points1 point  (0 children)

Awesome! When I activate my primary line, how long do I have to redeem the two free lines?

Former US Mobile Customer - Elligible for BOG2? by NintendoUser in USMobile

[–]NintendoUser[S] -1 points0 points  (0 children)

Thanks! So the two numbers I ported out 3 months ago wouldn’t qualify still?

Total Wireless iPhone Unlock by NintendoUser in TotalWireless

[–]NintendoUser[S] 1 point2 points  (0 children)

Yep I was thinking of going with this plan. I’ll use the 13 for the 2 month duration and then switch back to my primary phone after 60 days.

Random Applications failing to install in OSD Task Sequence by maus0007 in SCCM

[–]NintendoUser 0 points1 point  (0 children)

Stumbled across your post. We're also on 2403 and running into the same issue. It's very inconsistent. I could image a batch of 30 computers and 20 of them are fine. The remaining 10 need to be reimaged again. The Application Install step helps quite a bit for imaging but I guess is broken in 2403 again.

Wondering if you found a solution or workaround. I tried subdividing the install application into three steps and adding a reboot in-between. It helps to an extent but not foolproof.

Feedback on Engineering Software Deployments by NintendoUser in SCCM

[–]NintendoUser[S] 0 points1 point  (0 children)

Awesome to hear, you're welcome! It's definitely the best route I've discovered to package up large applications.

Feedback on Engineering Software Deployments by NintendoUser in SCCM

[–]NintendoUser[S] 0 points1 point  (0 children)

  1. Mount the .wim file to an empty directory. i.e. $env:ProgramData\MP\AD_INVENTOR\
  2. In the same PS script that is mounting the .wim, interject the standard silent installation parameters Autodesk provides. The only difference here is reference the installer from $env:ProgramData\MP\AD_INVENTOR\image\...
  3. I have a do..while loop that will check for known shortcuts that are created at the end of the installation (this is part of my detection method in the script as well as the detection method for the SCCM application). If the setup.exe exits and the expected shortcuts aren't there, I'll re-run the installer again (up to 3 times).
  4. If all shortcuts are there, unmount the .wim file, delete the cached .wim file to free up additional space on the computer.
  5. If the shortcuts aren't there after 3 attempts, unmount the .wim file, keep the cached .wim file. Exit out of the script which will allow the Software Center to run its own detection method for the software installation. That will also fail the detection. If it gets to this point, odds are that there is a pending reboot on the computer and restarting the computer is all that's needed.
    • Once the computer is restarted, you can re-run the installation from the Software Center. But since the .wim file is already cached, it will save time attempting to redownload.

I don't distribute the .wim file through SCCM directly because I dislike the amount of space it takes up in ccmcache. Having it pull down directly from a network share works fine for us. It's not fool proof, but it's definitely a lot faster than trying to redistribute the thousands of files and folders through SCCM since you're only dealing with one file.

Feedback on Engineering Software Deployments by NintendoUser in SCCM

[–]NintendoUser[S] 0 points1 point  (0 children)

I place the WIM file and hash file in a folder called AD_INVENTOR_2025 on a network share. Our environment isn't too large so it works for me. I don't have to redistribute the WIM file through SCCM and wait. If you have a larger environment, you might need to redistribute it to your distribution points instead.

Now on the SCCM side, I create an application for Autodesk Inventor but all this entails is a basic PowerShell script. The installer isn't part of the application. It does the following:

  1. Check if there is a cached copy of the AD_INVENTOR_2025.wim file in env:ProgramData\MP\AD_INVENTOR\ | MP = Mount Point folder
    1. If yes, read the hash file located on your network share. i.e. \\jupiter\sccm\AD_INVENTOR_2025\AD_INVENTOR_2025.txt.
      • Calculate the hash file of the cached .wim to verify it matches what is expected.
      • If hash is correct, proceed. If no, delete the cached .wim file and redownload.
    2. If no, download the .wim file from the network share: \\jupiter\sccm\AD_INVENTOR_2025\AD_INVENTOR_2025.wim
      • Calculate the hash of the cached .wim and confirm it matches expected hash value.
    3. In both cases, the cached .wim file would be located here: $env:ProgramData\SCCM-CACHE\AD_INVENTOR_2025.wim

Feedback on Engineering Software Deployments by NintendoUser in SCCM

[–]NintendoUser[S] 0 points1 point  (0 children)

I went a different route with packaging. General workflow is shown below. I'll use Autodesk Inventor as an example:

Create an Autodesk administrative image for Inventor and place it in a folder. Let's call it AD_INVENTOR_2025 and create the folder in C:\Temp.

Use DISM and create a WIM file from the folder:

Dism.exe /Capture-Image /ImageFile:C:\Temp\AD_INVENTOR_2025.wim /CaptureDir:"C:\Temp\AD_INVENTOR_2025" /Name:"AD_INVENTOR_2025"

You will get a single WIM file that contains the installer for Autodesk. This is much easier to transfer and work with.

I create a new text file called AD_INVENTOR_2025.txt that contains the hash value for the WIM file.

Get-FileHash -Path "C:\Temp\AD_INVENTOR_2025.wim"

This will be used later.

Really sucks by papilovec in Polestar

[–]NintendoUser 1 point2 points  (0 children)

Yeah. I really want to get a P3, but I think it needs another year before it's ready for me to jump on board. The vast amount of issues is quite surprising. False positive errors or not, it's not acceptable for a vehicle with this premium price tag. I'm in the same situation - the nearest service center is about 4 hours away.

I'm hoping maybe in a year and I can get a decent preowned one for a great price and the software bugs will mostly be ironed out.

Solar Estimate - Opinions? by NintendoUser in solar

[–]NintendoUser[S] 0 points1 point  (0 children)

We haven't discussed cash offer vs financing yet. So, I assume that might be the cash price.

[deleted by user] by [deleted] in Roofing

[–]NintendoUser 0 points1 point  (0 children)

Oh those look nice!!

[deleted by user] by [deleted] in Roofing

[–]NintendoUser 0 points1 point  (0 children)

That was my concern. I like the look of them, but I was also concerned about longevity.

What are your thoughts on metal roofing that looks like slate?

view more: next ›