Posts made by dbeato

Cool, looks like on the manual it ajows the bracket that holds it bur doesn't say the location. Nice to know though. I think it alsk depends pf the RAID card you use too.

@Eltolargo maybe they saw this post

@DustinB3403 is on the site, at least I see it released on 3/28

https://www.ubnt.com/download/unifi/unifi-ap-ac-lr

Welcome everyone!!

Putting the kids to bed!!

I'm waiting on Siemens 's MRI maintenance at our facility

We use Godaddy and Let's Encrypt.

@NerdyDad yep, they posted about this last week in SW.

@DustinB3403 it was only for me and no others.

@DustinB3403 I saw it over the weekend for about 30 minutes

@DustinB3403 and the new cloud tool

@Tim_G said in Install TeamViewer during "oobeSystem" (pass 7) WDS:

@NetworkNerd said in Install TeamViewer during "oobeSystem" (pass 7) WDS:

It's one thing to install TeamViewer but another to register with your TeamViewer account and enable unattended access, enforce policy, etc. I thought even if you downloaded the custom MSI you still had to make an API call back to TeamViewer to register the device with your TeamViewer account.

This is already taken care of with the .msi installer. No issues there. The issue is actually getting the .msi to run at the end of the image deployment. From what I understand, it's supposed to do it at the first logon of a user... and when the image is done, it logs on to a local admin user automatically. Does the normal dance before the desktop appears, but never any teamviewer install.

Take a look at this:
https://community.teamviewer.com/t5/Community-Blog/Deploy-TeamViewer-Host-Modules-to-Thousands-of-Devices-via/ba-p/3031

https://community.teamviewer.com/t5/TeamViewer-12/Installation-of-customised-TeamViewer-Host-via-GPO/td-p/1920

https://community.teamviewer.com/t5/Knowledge-Base/Deploy-TeamViewer-Host-MSI-Package-with-Assignment-Tool/ta-p/310

@NetworkNerd correct, deploying is easy is the actual activation that requires either a manual step or as you note.

Going for date night with the wife

@BBigford If we are talking about Office 365 Journaling is outdated while Litigation Hold and Compliance is the way to go. YOu can also still have a Mailbox Archive for each mailbox, but litigation hold will make it that any changes are not deleted from the mailbox.

http://windowsitpro.com/blog/why-exchange-online-hates-journal-mailboxes

Usually you will place a journaling mailbox on its own mailbox database due to the load of emails going to it for incoming and outgoing emails. The performance is not the goal but rather compliance as it gathers information as soon as it is sent or received.

An archive will tale what is already on or many mailboxes every so often that will allow for losing information at times.

Commuting to work now

Just watching NCIs with a cold one

@Tim_G that just plain sucks!!

@JaredBusch correct, I also have not seen it offered or done it myself.