Backtrack:  
 
showing posts tagged with 'software'
edited by on November 26th 2014, at 10:19

You can use the Guided Search Wizard for VMWare Compatibility Matrix to figure out if a certain version of ESX or feature is supported by a certain server or hardware platform:

http://www.vmware.com/resources/compatibility/wizard/request.php

edited by on November 20th 2014, at 15:47

If you have the Only-Search adware troubling you, you can download and run AdwareMedic. This is a simple and free adware removal tool.

Download: http://www.adwaremedic.com/index.php

edited by on November 20th 2014, at 15:16
Lingering objects in Active Directory are a pest, and require a lot of work to properly dispose of them. Luckily, there's repldiag.exe, part of Active Directory Utils. This particular tool resolves lingering objects by automating the required procedure and set of commands to run to clean up lingering objects.

In normal circumstances, you would have to look up and run various commands to completely clean out the AD database on each DC. Using repldiag.exe does the hard work for you by looking up the DC's and running the clean up on each DC, cross-referencing with the other DC's, and it does so by using the built-in commands and API's (such as those used by repladmin and other commands).

Down  ...
edited by on November 12th 2014, at 16:45

Technically, you can't set up out-of-office for shared mailboxes through a normal way, because you can't log in with Outlook on those accounts. A workaround would be to temporarily convert it to a regular mailbox, grant a license to it, and then log in with Outlook, but this is not always possible or desired.

Fortunately, you can also enable out-of-office through Powershell on any mailbox, including shared and resource mailboxes.

http://support.microsoft.com/kb/2667296

edited by on October 21st 2014, at 11:14
You can easily get a list of users and their assigned Office365 licenses through the Windows Azure Active Directory Module for PowerShell.

Connect to your Office365 tenant through a user with Administrator permissions:

Connect-MsolService

Then, enter this command:

Get-MsolUser | Select DisplayName,Licenses | FT

You can also append the following to export it to a CSV-file.

... | Export-CSV -Delimiter ";" ~Desktopmy-export.csv

The Licenses column tells which license is assigned, but it uses different names than what is visible at the WebPortal.

These are the ones that I know of:

STANDARDPACK Office365 Enterprise E1 ENTERPRISEPACK Office  ...
edited by on October 13th 2014, at 12:46
Installing a firmware upgrade on your Dell Force10 MXL IOM works similar (but slightly differently) than the other Force10 series. There are two things to upgrade: the IOM firmware and IOM operating system. The first has to be upgraded through CMC (not documented here), the second through the switch itself.

To upgrade FTOS, you need console access (can be SSH/Telnet) to the switch and an SCP/FTP/TFTP server.

If you have none of these, you can download tftp32/64. This is a light-weight TFTP-server which does not need to be installed and can be run as an application on any networked computer. Place the downloaded firmware (the BIN-file) in the same location as the tftp32/64 executable and st  ...
edited by on September 9th 2014, at 12:04

Shutdown the VM.

Open .vmx file with Notepad or another plain text editor.
Add these lines:

hypervisor.cpuid.v0 = "FALSE" 
mce.enable = "TRUE"
vhv.enable = "TRUE"
vpmc.enable = "TRUE"

Save and start the VM. Now you can install the Hyper-V role.

edited by on September 3rd 2014, at 14:56

Wanted to install the latest BES Express (at the time of writing, this was 5.0.4) on a fresh Windows-server. Starting Setup.exe briefly shows the Blackberry splash-screen, then immediately crashes ("this program has stopped working...").

Apparently, RIM did some sloppy programming: changing the regional settings to English (US) or English (UK) resolves the issue.

edited by on August 28th 2014, at 15:05
You can install the Exchange 2013 management tools on a standard workstation or on another server to remotely administer your Exchange 2013 servers. This is particular useful if you need to run Exchange Management Shell often, and don't want to log on to the Exchange-server in order to do so.

You need this:

A supported operating system, such as Windows 7, Windows 8, 2008R2, 2012, or 2012R2

The target computer must be domain-joined.

The following Windows Features: IIS 6 Metabase Compatibility

IIS 6 Management Console

IIS Management Console



and obviously: the Exchange 2013 DVD or ISO

For Windows 7 and 2008R2, these are extra:

Microsoft .NET Framework 4.5 (Windo  ...
edited by on August 28th 2014, at 13:11
For migrations from other e-mail platforms to Exchange, you probably want to have full access enabled for a certain Exchange-account to facilitate the migration without having to set up complex access rights. Exchange has something called application impersonation, which allows a user to impersonate other users to access individual mailboxes, which comes in very handy during a migration.

In order to set up application impersonation, you need access to the Exchange Management Shell (EMS), with an account which has permissions to set up access rights.

Exchange 2007 does not support application impersonation as in Exchange 2010 and up. Impersonation does exist but has to be set on each indivi  ...
edited by on August 28th 2014, at 13:09

If for some reason you need to enable Basic Authentication, you can do so quickly through the Exchange Management Shell. This is sometimes needed if you're migrating to Exchange from another (third-party) e-mail provider.

If you do not know what Basic Authentication is, you do not need this!

Start up EMS as an account which has the required permissions to make changes to the virtual directories used by Exchange. Then, run this:

Set-WebServicesVirtualDirectory -Identity "EWS (Default Web Site)" -BasicAuthentication $true

Note that Office365 has Basic Authentication enabled by default.

edited by on August 27th 2014, at 11:00
When using Veeam to back up your VMs, and you get the following error on one or more VMs:

Error: VSSControl: -2147212529 Backup job failed.Discovery phase failed.Cannot add volumes to the snapshot set.Cannot add a volume to the snapshot set. Volume name: [\\?\Volume{6c169bc7-d7bf-11e0-b074-806e6f6e6963}\].Cannot add volume to the set of volumes that should be shadowed.VSS error: VSS_E_UNEXPECTED_PROVIDER_ERROR. Code:0x8004230f

According to KB1785, this is because of a third party VSS provider, present on the VM. If more than the default software provider is installed, another third party backup software suite may have enabled their provider on the VM, causing the initiation of a VSS backup  ...
edited by on August 26th 2014, at 12:48

Direct links to the proofing tools. Select a language and download its proofing tools for free:

edited by on August 26th 2014, at 12:13
If the Windows Internal Database, used by WSUS, and which is actually an embedded SQL Server, is eating all of your memory, you can limit its memory usage the same way you would with a real SQL Server.

Open an elevated command prompt and launch the SQL prompt:

For WSUS4 (on Server 2012):

osql -E -S \.pipeMicrosoft##WIDtsqlquery

For WSUS3 (on Server 2008, 2008R2 and SBS 2008/2011)

osql -E -S \.pipemssql$microsoft##sseesqlquery

This will log you in with the current credentials (which is why it has to be an elevated command prompt). The SQL prompt (1>) is shown.

Enter the following commands to initiate advanced configuration:

exec sp_configure 'show advanced option', '1';reconfigure;  ...
edited by on August 25th 2014, at 12:30
When running ADFS 3.0 On a Windows 2012 R2 domain controller, on a reboot, the Active Directory Federation Services service may not start up properly, and may not subsequently not service requests. The Services management snap-in shows the service with a status of Starting.

The reason for this is an error during the deployment of ADFS where a dependent service, the Microsoft Key Distribution Service, is not set to start automatically, causing ADFS not to start up properly until that particular service is also started.

The solution is quite simple: in the Services management snap-in, find the service called Microsoft Key Distribution Service, and set its startup type to Automatic.

After th  ...
edited by on August 22nd 2014, at 12:44
In case you need to manually truncate the database logs of your Exchange server, you can follow the steps below. You'll need sufficient permissions and access to the Exchange Management Shell.

Caution!
Be cautious when you perform this action, as making mistakes here could cause database corruption and loss of data. Don't do this during production hours because this will temporarily make some (or all) mailboxes unavailable! As always, it's a good idea to have a working backup before attempting this.

Open the Exchange Management Shell.

If you don't know the physical path of your database, locate it first:

Get-MailboxDatabase | Select Name,EdbFilePath,LogFolderPath

You'll notice the datab  ...
edited by on August 20th 2014, at 10:12

Exchange stores plenty of things in Active Directory, including mailbox information for each account. In case of a deinstallation of Exchange, this information usually remains behind, making it impossible to perform a new clean installation of Exchange and assigning a new mailbox to this user.

I found a solution here: http://www.telnetport25.com/2009/09/forcing-the-removal-of-exchange-attributes-on-a-directory-user-the-removeexchangeattributes-tool%E2%80%A6/

This command-line tool allows you to query and/or remove Exchange-attributes on AD objects (such as users and groups).

edited by on August 14th 2014, at 14:17
In certain cases when deploying machines from a template using deployment customization, parts of this process may fail. As a result, upon each reboot, the system may try to re-run the customization process, and the following message is displayed at each startup:

VMware Image Customization in progress

To remove any pending sysprep customization routine, you can manually remove the reference to it by editing the Windows Registry

Start regedit.exe.

Navigate to the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\.

Change the value of BootExecute. Remove the part that says sysprepDecryptor.exe. Leave the other parts of the value as they were (so only remove the one w  ...
showing posts tagged with 'software'