Backtrack:  
 
showing posts tagged with 'computer'
edited by on January 8th 2014, at 12:34
Even though you've unchecked the time synchronisation checkbox in VMware Tools, synchronisation may still occur. Particularly when a certain action is performed, such as a power-off/power-on, suspend/resume, snapshot handling, etc., time synchronisation will still occur.

To complete disable time synchronisation, even during the events mentioned, you have to add additional parameters to the VMware VM configuration. There are two ways to do this.

Note that you need to have the machine powered off before you can do these changes.

Use a text editor to directly edit the .vmx-file, adding the required parameters:

tools.syncTime = "0"time.synchronize.continue = "0"time.synchronize.restore = "0"  ...
edited by on January 8th 2014, at 12:13
Remote Desktop Services shadowing is back with 2012 R2 after a leave of absence in regular 2012. However, for this to work out of the box, you need to have the scenario-based RDS deployment, which installs a whole bunch of stuff even when unwanted.

If you've opted for the roles-based installation of RDS Session Host (which is what makes your server into an RDS server), you're missing out on a whole lot of management tools, including the ability to shadow. Luckily, there are a few workarounds (using CLI) which provides us with the necessary things to perform shadowing.

Shadowing requires version 8.1 of the RDS client, so if you're not running Windows 8.1 or 2012 R2 on which you want to do t  ...
edited by on January 8th 2014, at 11:55

When performing RDS shadowing, by default, the user whose session is being shadowed has to consent to viewing and/or controlling his/her session. This behaviour can be changed with a group policy.

In your group policy (local or through domain), navigate to:

Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections

Find the policy called Set rules for remote control of Remote Desktop Services user sessions and configure it:

edited by on January 8th 2014, at 11:42

By default, only users with local admin rights on an RDS server can do session shadowing on that server.

To allow a particular user or group to allow shadowing, run this from a command prompt on the RDS server:

wmic /namespace:\\root\CIMV2\TerminalServices PATH Win32_TSPermissionsSetting WHERE (TerminalName="RDP-Tcp") CALL AddAccount "domain\group",2

In the command, replace domain\group with settings of your own. It's recommended to create a group specific for the job (e.g. RDS Shadowing) so you can run this command only once, and then add users to the group to allow them to shadow.

edited by on December 16th 2013, at 16:06

Before installing ROK licenses on your virtual machines on VMware, be sure to allow SMBios reflection of the host to the VM's. Otherwise, authorization will fail with a This system is unsupported message.

To do this, go to the settings of your newly created VM. Click the tab Configuration, then click General, then the button Configuration Parameters. Add a new row:

SMBIOS.reflectHost = TRUE

edited by on December 10th 2013, at 08:58
If for some reason a program window has wondered partially or completely off-screen, there are a few ways to get them back.

If you're running Windows 7 or newer, you can use the Windows key + an arrow key to align the window to a certain part of the screen the window is supposed to be on. This can also be used to reclaim your window, and get it back on the screen.

First, make sure the proper window or desktop app is activated by activating it on the task bar (click the corresponding button). Now, use either Windows + left arrow or Windows + right arrow to align the window to the left or right side of the screen, bringing it back entirely on the visible desktop. To give the window ba  ...
edited by on December 5th 2013, at 09:08

By default, when using a Telenet address on your smartphone, the Telenet mailserver (uit.telenet.be will not accept messages if they're not sent from within the Telenet network (e.g. when using Proximus, Mobistar or some other ISP or cellular operator).

You can resolve the issue by adding SMTP authentication to your outgoing mailserver settings. Simply add your username and password, and you will be able to send mail using Telenet SMTP.

edited by on November 28th 2013, at 10:45

A list of full installers for Windows (IE and other browsers), Mac OSX and linux is available here:

http://www.adobe.com/products/flashplayer/distribution3.html

It includes EXE and MSI-based installers, as well as profiles for use with SCCM.

edited by on November 15th 2013, at 16:05
After updating to OSX Mavericks, WebDAV no longer works properly. There's currently no solution available. Apple has released a workaround while they are attempting to fix the problem with the next update.

To workaround the issue, download the 3 files at this location:

http://www.opensource.apple.com/source/webdavfs/webdavfs-334.2/webdav_cert_ui.tproj/English.lproj/MainMenu.nib/

These 3 files will have to be placed in the folder:/System/Library/Filesystems/webdav.fs/Support/webdav_cert_ui.app/Contents/Resources/English.lproj/MainMenu.nib

You would normally overwrite the current ones present, but there's a catch. You can't simply overwrite the files because they are still in use by the sy  ...
edited by on November 6th 2013, at 11:23
After installing updates for Sharepoint on a SBS 2011, you may experience backup failures. The most common error is a problem with Volume Shadow Copy (error 0x800423f0 or 0x800423f3).

The error is occured because updating Sharepoint 2010 is a two-step process. Installing the updates will update the binaries, but you still manually have to update the database by running the database update command.

To determine whether you really need the update, you can run the following command from an elevated Sharepoint 2010 Management shell (available from the start menu):

PS C:> (get-spserver $env:computername).NeedsUpgradeTruePS C:>

When the result returns True, the upgrade is neede  ...
edited by on October 3rd 2013, at 16:50
Users of the newly released Remote Desktop Manager 9.0 will notice that there's now a 64-bit version installed alongside the 32-bit version. Upon running this 64-bit version, you'll notice how much slower it is than the 32-bit version. I posted it on the Devolutions forum and got this reply, designating it as a known issue with 64-bit .NET.

Quote
Hi,
Unfortunately this is known issue with .NET 64.

http://stackoverflow.com/questions/12979774/net-4-0-app-slower-on-64-bit-than-32-bit-profiling-and-possible-solutions-ap

By the way we recommend to use the 32 bit version of RDM ans switch to the 64 version only if you get some memory limitation. We have more technology  ...
edited by on October 1st 2013, at 10:47
If you have issues after upgrading to a newer version of Symantec Endpoint Protection Manager, check out the logs at .tomcatlogs. There's a file called catalina.err which usually provides some degree of more useful error messages than the one in Windows Event logs. Additionally, other files such as scm-server.log are also useful.

Sometimes after upgrading, the Upgrade Wizard does not run, and the database does not get updated, resulting in SEPM not starting up. A look in the catalina.err reveals that the the database schema and server schema are not compliant.

You can manually run the Upgrade Wizard. Navigate to .bin and run the script upgrade.bat. It will start the wizard and continue wit  ...
edited by on September 30th 2013, at 09:51
You can change/set the From-addresses in FreePBX to something you want.

Change the address in Admin » System Admin. To the right, click on Notification Settings, then fill in the From Address.

These are set up from within Asterisk, and are located at Settings » Voicemail Admin. Click on the Settings link, then scroll down until you find serveremail. Change it to whatever you want.

Next, because it uses Postfix to e-mail out voicemail notifications, you'll also have to change a parameter in there:

Open a shell to your box (SSH).

Type nano /etc/postfix/main.cf.

Find and change, or add a line: mydomain your-domain-name.com. Fill in the domain you want. It should be the same as  ...
edited by on September 11th 2013, at 15:11

If you have an HP laptop with an unknown device with hardware-id HPQ6001, it's the HP wireless button driver. Apparently some models on their support website lack this driver in the download list (it was the case for a HP Envy Touchsmart 1230eb).

Direct link to download: http://ftp.hp.com/pub/softpaq/sp58501-59000/sp58720.exe

edited by on September 11th 2013, at 15:02

If you happen to stumble upon an unknown device in Windows Device Manager with a hardware ID of ACPI\INT33A0, it's the Intel Smart Connect Technology device. Download its driver from Intel or from your manufacturer's website.

edited by on September 3rd 2013, at 10:21

You can clear the WINS cache (NBT) by using the command prompt in a similar fashion as clearing the DNS cache:

nbtstat -R

Note that this only clears the cache. Normally you would want to repopulate it by running a new discovery (reregistration) on the network, like so:

nbtstat -RR
edited by on August 23rd 2013, at 09:23
Since Windows 2008 and certain versions of 2003, automounting of iSCSI volumes is enabled by default. While this is fine for most setups, it is sometimes required that the volumes on your iSCSI targets are not automatically mounted when the server starts up (e.g. on a VMware backup server where you don't want to mount VMFS volumes).

There are several ways to disable automount.

Open an elevated command prompt and run either:

mountvol /N

or

diskpart automount disable

This will turn off automount so volumes will not be mounted automatically on a next reboot.

You can verify (and set) the automount status through the registry. Look at the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSe  ...
edited by on August 22nd 2013, at 15:53

A note about installing the drivers for the Dell PowerVault TL2000/4000 on a Windows 2012 machine.

You can download the firmware from the Dell Support website. After extracting the package, do not install the driver using Device Manager. Doing so will not properly install the drivers (results in error code 37). Instead, install them using the included executable (install_nonexclusive.exe). Running this (elevated) will install the drivers the proper way, and the devices will start correctly.

edited by on August 21st 2013, at 10:18
I've encountered several issues on different HP Elitebook Folio 9470m ultrabooks, after updating the BIOS to its latest version (F.46).

One series of ultrabooks with an Intel Hybrid HD (with SSD cache) suddenly stopped working with a BSOD and refused to startup. Reinstallation with the original DVD oddly failed as well, either during installation, or after installing drivers. We've worked around the issue by using a Microsoft (non-HP) DVD to install Windows 8, then download the latest drivers from the HP site.

Another ultrabook with an SSD had another problem altogether, but still related to the BIOS update. After the update, USB devices started to fail intermittently. Both the   ...
showing posts tagged with 'computer'
 
 
« June 2024»
SunMonTueWedThuFriSat
      1
2345678
9101112131415
16171819202122
23242526272829
30      
 
Links
 
Quote
« If the batteries of a TV remote run out, why do we press the buttons so much harder? »