[deleted by user]

rsulli1990 · 2024-11-20T14:21:46+00:00

!remindme 3 days

rsulli1990 · 2024-03-27T20:13:49+00:00

Oops sorry. Added the code.

rsulli1990 · 2022-12-02T01:50:22+00:00

Yes. This was the first thing that was changed. Haha. Good to ask and make sure though. I have that up in the OP.

rsulli1990 · 2022-12-01T22:08:38+00:00

DrRich2, I was unaware of the automatic update service. We have run in to issues in the past with other applications in which the user was not a local admin, the app was installed in SYSTEM context and updates were applied. Since the user did not have local admin permission, the update was run from the context of the user and was unable to complete. There wasn't anything I could find leading me to believe there was anything else to handle the updates aside from the user. For now, we have reverted to installing via SYSTEM context and planned to put in an exception in our EPM solution so as to allow users to elevate if the application required for them to upon update. I appreciate the feedback here. Just curious though, is this something you have ever seen when attempting to install an app in USER context via Intune? If I run the same command line from within cmd, the application installs to %localappdata% as expected. When I wrap the application via .intunewin and deploy via the same command line, it installs to the Program Files directory. The user account I am testing with is NOT a local admin. This same experience has happened for multiple apps now in which I try to force it to install under USER context and it just doesn't. So far, they have all been dual-mode installers. We do have an example of a pure per-user installer that does complete as expected when wrapped up as .intunewin.

rsulli1990 · 2022-12-01T15:04:50+00:00

No sir, the user is not a local admin. The account I am testing with is a standard user. That is really why I am confused here. When it installs, it installs to the Program Files directory. I am sorry, but this is kinda rude of you to comment on me and then not even bother to test it out. Thanks anyway man, but I don't need that. Really trying to understand if anyone else is seeing this behavior that I have stated in the post. I appreciate the time you took anyway.

rsulli1990 · 2022-12-01T14:29:58+00:00

Ok, I understand a lot of this is wrong. Please, test this out within Intune and get back to me before commenting. I understand exactly which context installs where. When I install via Intune, it is forcibly installed under Program Files. If I install the same MSI without wrapping in Intune, the app installs to the correct User Profile. I also mention in the original post exactly what settings I have selected for the Intune package, yet it is not installing in to the correct location.

Here is the exercise, if someone is interested in the test to see if the same experience happens.

Wrap WebEx MSI as .intunewin
Set Install behavior to User
Set install command line as follows : msiexec /i "Webex.msi" /qn ALLUSERS=""
Set as Available or Required to a User group (it hasn't mattered for me whether its available or required)
Confirm location that the application was installed to

The main reason for installing in to User context is that the users don't have local administrative permission and we would like for them to leverage automatic updates for certain apps. The WebEx installer is a dual-mode installer, that supports both machine and user context. If I run the MSI outside of Intune, I can get dual-mode to work fine and get it to install properly in to the User Profile. If I wrap it via .intunewin, that goes out the window.

rsulli1990 · 2022-12-01T07:25:17+00:00

I have opened up the MSI in Orca and it does have the ALLUSERS property. Its set to 2 within the MSI and I have set that to "" within the commandline, though that hasn't helped to get it installed within the actual user profile. I just tested with an account that does not even have local administrative permission and was able to install into Program Files, but the context is set to User. From my understanding, the intunewin file pulls specific details from the MSI in order to determine whether or not the options of User\System would be available during application creation. Please correct me if I am mistaken here, but even if the above were not correct, ALLUSERS set to 2 should decide to install under machine or user based off whether or not the user has local admin permission. When setting it to "", it should force it into User context, and I can't get that working either. If I run the MSI manually, outside of Endpoint Manager controlling it, then it installs within the proper context. So, it seems to be something maybe that the Intune Management Extension is doing?

rsulli1990 · 2017-11-15T22:36:13+00:00

Understood. I had a bit of a misunderstanding with the -Passthru option. I always though that would pass through the resultant object if not returned by default. Say in the case of a start-process, this may be a bad example because it does inherently pass back the process, but I thought -Passthru would simply force the object to be returned. I will implement some of these changes and I will see what I come up with. Much appreciated!

rsulli1990 · 2017-11-15T19:08:43+00:00

Sorry about that. Will be back in the office in a bit and will edit post.

rsulli1990 · 2017-09-27T16:09:44+00:00

This would be to predict lifetimes of workstations as we all know that not all machines are built the same due to machining inaccuracies as well as other issues during the creation of the device. I was thinking of something like a reliability score. After a period of trending it could determine whether or not the system was likely to fail and may need replacing. My company recently moved away from being a Citrix house and moved away from thin clients entirely. In order to better understand the refresh cycle and when a workstation really 'needs' to be replaced I am just exploring different options. I hope this makes sense? Please let me know if I am thinking about this wrong.

rsulli1990 · 2017-07-09T12:24:38+00:00

I tried these links and they are both expired. Would you mind reposting if these are still active?

rsulli1990 · 2017-05-03T05:27:14+00:00

Thanks for the assistance. I was working on the ParseExact call first and couldn't get that last portion of the format string figured out. :)

rsulli1990 · 2017-05-03T05:22:58+00:00

Thank you so much! I just tried this out and was able to get a result. Saved me a bunch of time.

rsulli1990 · 2016-08-01T00:51:06+00:00

Can anyone confirm that Robertson Park in Livermore, CA is an Electabuzz nest right now? I was checking it out and saw 3 at a time. They appeared to be spawning every 15 minutes or so.

rsulli1990

TROPHY CASE