@Dashrender said:
Here is what I see for a drop down on attachments in O365 email.
There's a folder called "Email Attachments" It creates.
@Dashrender said:
Here is what I see for a drop down on attachments in O365 email.
There's a folder called "Email Attachments" It creates.
@TAHIN said:
and servers/SANs. The MSA series SAN is crap,
All of Dells/EQ SANs are. They are entry level SANs at best. None of them are Enterprise grade.
@aaron said:
With 10 offices I would definitely use managed switches, especially for monitoring. I've driven hours before to power cycle a switch.
None of that implies a managed switch. a PDU would be far more useful. You can't really get in to locked up managed switch remotely anyway.
@Dashrender said:
and even so - that doesn't make it safer.
Google also wraps your login inside a SSL connection - but you can still attempt to log in until their system denies you for to man invalid attempts.
It does make it safer. There is no way to stop what you are saying. You can do this with VPNs. Logins that require RSA Keys etc. That's why you have lock outs. We have ours set to three.
Most large companies have Ctirix or RD Gateways. A VPN is unusually only for company owned devices and is more of a risk because it exposes the whole network directly to the device once logged in.
@aaron said:
Depending on the business need. OP asked for reasons to use a managed switch. We could dive deeper into routing, hot swappable PSUs, etc. I just mentioned a few reasons off the top of my head.
You have to be pretty high end to have hot swappable PSUs in switches. Even our access layer switches do not use them. I dobut a small company of 500 is getting into hot swappable switch PSUs at all.
looking at this script is there a way to make it so it works on two domians? ex from is domain A to is domain B.
There is a trust in place, and can be done manually but it's a lot of work to do manually.
This worked
import-module ActiveDirectory
cls
write-output "This script adds the destination user to all the Groups which the source user is memberof."
write-output " "
write-output " "
$SName = Read-Host "Please Enter the alias name of the source user "
$DName = Read-Host "Please Enter the alias name of the Destination user "
$DN = Get-ADUser $DName -Server DOMAINBDC
$K = Get-ADUser -Identity $SName -Properties memberOf
foreach($group in $K.memberof)
{
Add-ADGroupMember -Identity $group -Member $DN
write-output $group
}
@Dashrender said:
Thanks - I have one customer with one of these.. might be time to change to a ERL
It's an easy upgrade Just upgrade to the ASA version not affected.
@aaron said:
It is 2016, not 1969-12-31, why would you do that?
It's about software bugs.
@johnhooks said:
@NetworkNerd said:
Unifi controller VM (servicing all sites) - 1 VM as controller for APs across all sites
This probably won't make a big difference at all, but could this be put on a hosted VM somewhere? That would at least alleviate restoring this VM if something happens.
That wouldn't make sense. At least not for the reasons you state. Remember there needs to be valid business reasons for doing this. In the Case of DR it's to provide business continuity. What business disruption will be caused if the unifi controller is down?
@johnhooks said:
@Jason said:
@johnhooks said:
@NetworkNerd said:
Unifi controller VM (servicing all sites) - 1 VM as controller for APs across all sites
This probably won't make a big difference at all, but could this be put on a hosted VM somewhere? That would at least alleviate restoring this VM if something happens.
That wouldn't make sense. At least not for the reasons you state. Remember there needs to be valid business reasons for doing this. In the Case of DR it's to provide business continuity. What business disruption will be caused if the unifi controller is down?
There most likely wouldn't be a disruption, but it's one less thing to worry about in a DR situation and it helps with this issue
You wouldn't be worrying about something that provides no business continuity in a DR situation. That would be something you can deal with much later. The focus should be on things that directly have a monetary impact on the business.
@johnhooks said:
15 GB is the min disk size and then I read a few places where people had issues with Java overtaking resources if they had below 1 GB of RAM. So it is minimal, but it also seems like a lot for what it does.
That doesn't mean that's what is actually used. Also Dedupe like @scottalanmiller will make the base OS images take the same just just one instance. and the unifi controller itself is very little storage.
@johnhooks said:
@scottalanmiller said:
@johnhooks said:
15 GB is the min disk size and then I read a few places where people had issues with Java overtaking resources if they had below 1 GB of RAM. So it is minimal, but it also seems like a lot for what it does.
Min size for what? We provision new PBXs smaller than that. Uses almost nothing. We have them running in 256MB without a problem (although 380MB would be nice.)
The database will crash if you have less than 15 GB disk space. I tried 10 and it wouldn't work until I gave it 15. It's terrible, but everyone else I read had the same issue.
Think provisioning will still use less. I haven't ran into that issue.
@NetworkNerd said:
@Jason said:
@johnhooks said:
15 GB is the min disk size and then I read a few places where people had issues with Java overtaking resources if they had below 1 GB of RAM. So it is minimal, but it also seems like a lot for what it does.
That doesn't mean that's what is actually used. Also Dedupe like @scottalanmiller will make the base OS images take the same just just one instance. and the unifi controller itself is very little storage.
I assume you mean dedupe as it relates to backup and replication jobs and not to the data stored in the actual datastore running on local storage of each host.
You can dedupe the live storage, if you are using local and not a SAN with ESXi you'd need to use something between that local storage and ESXi to do it (like a VSAN software).
Most ticket systems allow you to change how often it polls the email inbox.
@wirestyle22 said:
@scottalanmiller said:
@wirestyle22 said:
@scottalanmiller said:
Well the purpose of LMI is to bypass the need for a connection like ZT. Having ZT you can just go back to use RDP, ICA, NX or whatever like you used before LMI.
I mean, could I realistically run everything from a remote server and have a thin client with ZT installed just view it?
ZT is just a nice VPN. So if a thin client would have worked before, it will keep working with ZT. If the thin client worked with a VPN before, it will work with ZT. ZT doesnt really add anything new to a thin client / terminal server model. It works fine there, but I'm not picturing what you feel is the new feature here.
We have had no thin client before I'm just wondering with distance and everything involved if it's a reasonable alternative
Why would you use ZT instead of an RD Gateway? With VPN your exposing more to the external thin client.
@FATeknollogee said:
Type 3: Users (are contractors), they connect via VPN from overseas
Seems like a bad idea. Usually employees are given VPN access from company owned devices. a VPN is too much exposure for non-company owned devices and for people who aren't full employees. I would look into some other form of access, RD Gateway with RDS or Ctirix etc for these people.
@Dashrender said:
I built a new FB profile just for use at my office - to control business related matters on FB.
There's you're first problem. It shouldn't be an IT thing. that's PR/HR and Legal's thing.