As found on Voip-info.org, a list of bandwidth consumption per codec.
It's worth mentioning that the table also indicates the total consumption including IP overhead. When making assumptions about bandwidth requirements, it is useful to take this overhead into account.
|G.711||64 Kbps||87.2 Kbps|
|G.729||8 Kbps||31.2 Kbps|
|G.723.1||6.4 Kbps||21.9 Kbps|
|G.723.1||5.3 Kbps||20.8 Kbps|
|G.726||32 Kbps||55.2 Kbps|
|G.726||24 Kbps||47.2 Kbps|
|G.728||16 Kbps||31.5 Kbps|
|iLBC||15 Kbps||27.7 Kbps|
You can easily verify whether an ADFS implementation is working by using a browser and trying to log on:
Replace adfs.yourdomain.com accordingly.
Note that in 2016, this no longer works unless you re-enable this feature through Powershell:
Set-AdfsProperties -EnableIdpInitiatedSignonPage $true
The RLM module may become unresponsive and you may see the following messages in the Syslog:
You can resolve the issue by rebooting the RLM from the CLI.
Log on using the CLI (SSH or console), then reboot the RLM.
CLI: rlm reboot
Wait for a while and verify the RLM is back online:
CLI: rlm status
The output of the command should report: Status: Online
I got this through the contact form. It's a jargon-free guide to computer and internet security. It provides a detailed explanation on how to properly secure your computer and internet experience, and best of all, it uses simple and understandable language, lowering the bar for everyone to secure themselves against malware, ransomware and other malicious attacks.
Although unsupported, it is possible to install Microsoft Security Essentials on a Windows Server 2012.
To do this, set the compatibility of the downloaded file to Windows 7, then start that file with the parameter /disableoslimit.
The installation goes without a problem, and as far as I can tell, there are no compatibility issues.
If for any reason you need to determine whether a specific instance of VMWare View Connection Server is installed as a standalone server or a replica server, you can do so by looking into the registry.
In HKEY_LOCAL_MACHINE\Software\VMware, Inc.\VMware VDM, the value ServerInstanceType will indicate which type the CS is:
1 = standalone/first CS
2 = replica CS
Note that this doesn't really matter, as the only difference between them is whether they set up a new ADAM instance or connect to an existing one. After the installation of VCS, they are identical.
You can very easily properly uninstall the Palo Alto GlobalProtect client on Mac OSX by running the included uninstallation script:
Open a Terminal and then run it by typing:
Provide your password when asked and the script will uninstall GlobalProtect.
One of the most common Exchange admin tasks is setting mailbox delegations. Personally, I usually do this through EAC but once you're familiar with the Powershell counterparts, it can be quicker to use that instead. I've created this post as a reference to do just that.
In the reference below, the user "Ellen Somebody" requires access to the mailbox of "John Doe".
Send on Behalf
Set-Mailbox john.doe -GrantSendOnBehalfTo ellen.somebody
Add-ADPermission john.doe -ExtendedRights Send-As -user ellen.somebody
Add-MailboxPermission -Identity john.doe -User ellen.somebody -AccessRights FullAccess -InheritanceType All
Hyper-V does not allow to be installed on a machine that's already virtual (such as on another Hyper-V or VMWare). For VMWare, you can circumvent this by adding custom configuration parameters to the VM's configuration.
Add these to the VM's configuration, either through the vSphere (web)client, or by directly editing the VMX-file:
hvh.enable = TRUE hypervisor.cpuid.v0 = FALSE
If you're editing the VMX-file, you need to enclose the values (behind the =) in double quotes (").
Older, obsolete releases of Ubuntu are no longer available on localized mirrors. Instead, you must use the old-releases repositories. This is done by replacing the repository entries in /etc/apt/sources.list:
You can easily run Transact-SQL (T-SQL) script files (with extension .sql) via the commandline utility sqlcmd:
sqlcmd -S Server\Instance -i C:\path\to\SomeScript.sql
By default, the output is written to the command prompt. You can also save the output to a file:
sqlcmd -S Server\Instance -i C:\path\to\SomeScript.sql -o C:\path\to\TheOutput.txt
Note that when using this, no output is written in the command prompt window.