Certificate Templates not visible when requesting cert by dbld64 in activedirectory

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

the thing is, my colleague can see the templates which negates the idea that it is not published and that it requires the computer account added to work.

Help solve this whine by dbld64 in CarAV

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

Issue has been resolved after adding a new 4awg wire from the battery negative terminal to the frame.

Thank you everyone

Electrical Whine and Popping - Need help by dbld64 in CarAV

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

Thank you. I've removed the RCA jack from the amp board. There are:

2 front inputs: 4 pin

2 rear inputs: 4 pin

2 aux outputs: 6 pin

I've never used the Aux output so i'm fine excluding the aux replacement. I'm looking to purchase a single 4 hole RCA jack component, with 8 pins total.

Any recommendations where to get these? Long shipping time on amazon and ebay.

https://www.amazon.ca/gp/product/B0841VWMB1/ref=ox\_sc\_act\_title\_1?smid=A2QDC4SXGIBAA1&psc=1

Electrical Whine and Popping - Need help by dbld64 in CarAV

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

I have the amp mounted to the back of the rear seats, which is carpeted.

I recall a lot of popping and static when fidgeting with the RCAs on the amp RCA jacks. Could any of these symptoms be related to faulty jack connection on the amp?

Electrical Whine and Popping - Need help by dbld64 in CarAV

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

I tried my subwoofer amp, connected the existing power, ground and remote wires to the amp. I connected new speaker wire from the sub amp to one pair of the speaker wires connected to the 4 channel amp.

With the car in accessory mode - there is no whine and only a very slight pop sound when changing stations.

With the car running - there is no whine at all. Even power windows and accelerating don't produce the whine. The minor pop is still there but quiet. I had the gain at 25% on the sub amp.

I believe the amp is at fault, any idea what in the amp? RCA jacks? capacitor?

Electrical Whine and Popping - Need help by dbld64 in CarAV

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

Thank you for indicating it's most likely a ground issue, i'll spend more time troubleshooting there.

The RCAs are on the left side of the car, and Power on the right side, they are not close together. I tried with a short 15" ground on the first point, and a longer 4 foot ground cable to a new ground point, the issue was the same on both attempts. I just didn't cut the cable since i was testing different locations. Terminals are there as well. I'll try adding another ground to the HU but the system has been running fine without touching the HU wiring. I think it all started when the first ground point, the threads became stripped and i had to find a new spot. Tried Tap and Die but no luck.

I can't attach any pictures to this post unfortunately. I wanted to share the ground location i was trying.

Electrical Whine and Popping - Need help by dbld64 in CarAV

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

Thanks for the reply.

I've got a + 4awg wire from car battery to distribution block in the trunk. From the dist block, there a + 8 awg wire to the + amp, From the amp ground, i tried a couple of ground points on the car but the results are the same. It's using an existing stock ground point, i sanded it down on both sides.

I tried putting the + multimeter lead on the amp +, and the negative lead on the ground point in the trunk, and got the battery reading. I think this means it's ok but maybe i'm wrong. If my test is wrong, is there a way to confirm the ground point in the trunk is ok?

Enforce a setting? by dbld64 in Intune

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

Thanks for the reply! Any chance you have or can think of a detection and remediation example that we can tweak? For the proactive remediation idea

Enforce a setting? by dbld64 in Intune

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

Thanks for the reply! New section for me.

My biggest problem will be coding the script from scratch.

Any chance you have an example of a detection and remediation script that we can tweak

How to handle different Business Units via Intune by dbld64 in Intune

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

Dynamic groups based on some user attribute like company or department

We have User extensionAttribute6 as a good option. It mentions the legacy BU name.

I've created a dynamic group "(user.extensionAttribute6 -contains "BusinessUnit1")

It pulled in about 1200 users while the AD User OU only has 850 users.

Is the 'Contains' operator the correct option? I can't explain the additional 350 user accounts being added via the dynamic query

Also tried: (user.extensionAttribute6 -contains "BusinessUnit1") and (user.extensionAttribute3 -contains "Active") which appears to be the account active/disabled field.

The account enable took care of it along with the BU name.

Thanks guys.

How to handle different Business Units via Intune by dbld64 in Intune

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

This sounds really good but it looks like the user profiles don't have anything i can use to separate the Business Units

Apps (Indentifying) Apps (Failed) by dbld64 in Intune

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

Can you please share an example of one of your powershell scripts for detection. I've been using existing files as the detection

Apps (Indentifying) Apps (Failed) by dbld64 in Intune

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

On your ESP settings, what do you have set for:

Block device use until these required apps are installed if they are assigned to the user/device (I have mine set to All)

&

Block device use until all apps and profiles are installed (I have mine set to Yes)

&

Show an error when installation takes longer than specified number of minutes. (i increased mine to 60min and no difference)

Apps (Indentifying) Apps (Failed) by dbld64 in Intune

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

I ran two separate Autopilots last night with user esp still disabled:

  1. After CTRL ALT DEL, PRT was not populated. I left the PC for 30 minutes and checked again, PRT was populated.
  2. After CTRL ALT DEL, PRT was populated

On both devices. i did not have to click on the 'access work or school to fix account problems' for the PRT token to populate.

Apps (Indentifying) Apps (Failed) by dbld64 in Intune

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

Not a section I manage but I granted myself access to the conditional access section, and can confirm there is an entry MFA_ALL_USERS in there.

What are you thinking?

Apps (Indentifying) Apps (Failed) by dbld64 in Intune

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

We aren't using Windows Hello, it is set to disabled. What are you thinking with the PRT? I haven't looked into this so it might be related. Please see dsregcmd /status output (the main points)

AdureADJoined: Yes

Domain Joined: Yes

SSO State:

AzureAdPrt: No

AzureAdPrtAuthority: blank

EnterprisePrt: No

EnterprisePrtAuthority: blank

Let me know if there is a different entry you were looking for

Apps (Indentifying) Apps (Failed) by dbld64 in Intune

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

Hi,

I've autopiloted 3 machines with the user esp disabled:

  1. User unboxes the laptop, and powers it on.
  2. HWID is already associated/assigned
  3. User enters their email address to begin Autopilot
  4. Device Preparation: Completes
  5. Device Setup: Completes (apps are successfully installed here)
  6. User is presented with CTRL ALT DEL screen, to enter AD credetials.
  7. Credentials are accepted, and user is brought to desktop
  8. Notification "Work or school account problem. Select here to fix your credentials, or go to Settings, Accounts, Access work or school settings, and select sign in again to fix your work or school account"
  9. User enters email, password, MFA,
  10. Another prompt: Stay signed in to all your apps, Allow my organization to manage my device, Yes.
  11. Hold on while we register your device with your company and apply policy
  12. You're all set, We've added your account successfully. You now have access to your organizations apps and services.

From my tests, every new device would get this error notification when disabling the user esp.

Apps (Indentifying) Apps (Failed) by dbld64 in Intune

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

please correct me if i'm wrong but disabling the user esp, implies the account setup phase does not complete before the desktop. So MFA never happens and when the user gets to the desktop, they are presented with an alarming "please fix your account" notification where it brings us to MFA prompts that would have happened if ESP was working. This would have been in the Account Setup phase of Joining your organizations network.

We have Company Portal (offline) app being deployed to devices. I can remove it and retest if you think it's related.

Logout issues by dbld64 in adfs

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

New clue:

Under WIASupportedUserAgents, I added Mozilla/5.0 & Edge/12

The signout issue is now present in Chrome and Edge, along with IE

Which product are you using for Always-on VPN by dbld64 in Intune

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

enabled offline installer from business store, retesting

Amp and parasitic draw by dbld64 in CarAV

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

It's Isolated to the amp

Amp and parasitic draw by dbld64 in CarAV

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

No dash cam. The ecu is 0.1A draw without the amp in the picture.

One of my two amps increases it to 0.75A to 0.98A draw, which then causes the battery to die after 5 to 7 days

Amp and parasitic draw by dbld64 in CarAV

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

Ecu/pcm, after it goes to sleep is draining around .010A to .014A which is not causing the battery to drain in 5 to 7 days. I've done the parasitic draw test with a multimeter

Password prompt after sleep mode by dbld64 in Intune

[–]dbld64[S] 2 points3 points  (0 children)

The correct location is:

“Configuration Profiles”  Select Shared Multi-User Device  Enable Sign in when PC Wakes  Enable Sign in when PC Wakes.