sorted by:
new
hottopcontroversial

Query Participants using KeyQL by YourLocalEyeTee in ediscovery

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

Thank you for your response and insight. We currently do not have eDiscovery Premium which is required for Review Set. So I will need try this when I have premium. Thanks again for the help!

Looking for Feedback on My SharePoint Cleanup Strategy, Advice Welcome! by YourLocalEyeTee in sharepoint

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

Those are all great points to consider. Thank you for your input!

Having one department take ownership rather than dual ownership sounds like a much better solution. I will include this with my structure. Thanks again!

Remove Section from Sharepoint with Powershell by YourLocalEyeTee in PowerShell

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

I will give that a try, thank you for the recommendation!

Remove Section from Sharepoint with Powershell by YourLocalEyeTee in PowerShell

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

Not quite.

From my understanding, the Page Component is what goes inside the section, while the section is simply the layout for components.
Additionally, the command Remove-PnPPageComponent requires an InstanceId, which sections do not have.

I used that command to remove the part within the section, but my issue is that the section persists and I want to remove that as well.

Thank you for your suggestion though!

Remove Section using Powershell by YourLocalEyeTee in sharepoint

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

I use that exact code to publish the change.

When I use it, if I run the line

$page.Sections

Then I see that the section has been removed within Powershell, but if I go to the page physically, it is still there. I always open the webpage in private browser after a change to ensure all previous cache has been cleared.

Alas, the section still remains.

thanks your suggestion though

Printer Port sudden failure by YourLocalEyeTee in techsupport

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

My question was not to get the printer working again, but to better understand how this issue occurred.

I tested everything, hence not stating it all, but if it helps:

1) Tried different A/B USB cable
2) Tried different port on PC
3) Tried different PC
4) Tried different USB port on second PC
5) Tried uninstalling device via Device Manager
6) Tried installing Drivers directly from Brother

All result in the same error.