Backtrack:  
 
showing posts tagged with 'windows'
edited by on February 18th 2014, at 11:48

Found this online: ClickYes software. Don't install!

It's supposed to automatically click Yes when a program uses Outlook to send e-mail. In my opinion, it's a very useless piece of software as one could simply disable the prompt in Outlook, or better, install a proper antivirus.

edited by on February 14th 2014, at 09:54

If you're running Internet Explorer 10 or later, you may get this error when trying to log on to a computer using RDP through Remote Web Workplace:

You can resolve the issue by adding RWW to the Compatibility View list in Internet Explorer.

edited by on February 14th 2014, at 09:33
If you have users that were created in AD but not through the SBS console, you'll notice they will not be present in the SBS console. This can be a nuisance for management purposes when you're used to using the SBS console for administering users, but it can also become a problem for some SBS functionality, such as the SBS POP3 Connector. There is a way for your users to be added to the SBS console without having to recreate them, though.

When querying the list of users, the SBS console in fact looks for a certain AD attribute inside each user. This attribute, when set, will enable listing in the SBS console. So, by setting the attribute, you will in fact "import" the us  ...
edited by on February 14th 2014, at 09:31

You can add RDS servers to the list of computers in Remote Web Workplace, making them available to anyone with access to RWW. The process is simple, requires no reboot and is immediately active.

  1. Fire up regedit.
  2. Navigate to HKEY_LOCAL_MACHINE\Microsoft\SmallBusinessServer.
  3. Add a new key called RemoteUserPortal.
  4. Under the new key, create a MultiString value called TsServerNames. Edit the value and insert the name (FQDN or NBN) of your RDS server. If you have more than one, add them on separate lines.

Note that this will only work if your RDS server is inside the SBSServers OU or a sub-OU (i.e. you're allowed to create other OU's inside the SBSServers OU).

edited by on February 13th 2014, at 12:12
If for some mysterious, unknown reason, your backup suddenly stops working and throws VSS errors, it's usually a good idea to check the following:

If your server is an SBS 2008 or 2011, and have installed updates, you may have to reconfigure Sharepoint:
WSB fails on SBS 2011 after updating Sharepoint (0x800423f0 or 0x800423f3).

If you get errors about VSS failing to create a snapshot, and you have not changed anything on your server recently, it's a good idea to check the presence of a lot of old shadow copies, taking up space. Although old copies will be purged automatically, the VSS Writer doesn't wait around for it, and fails the backup.
So try deleting shadow copies or increase the sh  ...
edited by on February 11th 2014, at 13:52

To get this card running on Windows Server 2012 and 2012 R2, you need this driver:

https://downloadcenter.intel.com/confirm.aspx?httpDown=http://downloadmirror.intel.com/18720/eng/PROWinx64.exe&lang=eng&Dwnldid=18720

Newer versions no longer seem to support this card.

edited by on February 5th 2014, at 16:45

Run this command in an elevated Powershell to enable remote WMI access:

Enable-NetFirewallRule -Name WMI-RPCSS-In-TCP,WMI-WINMGMT-In-TCP,WMI-WINMGMT-Out-TCP,WMI-ASYNC-In-TCP
edited by on February 3rd 2014, at 08:39

A handy tool to edit file associations, default program handlers, and autoplay handlers:

http://defaultprogramseditor.com/

And best of all, it's free!

edited by on January 29th 2014, at 08:57
Users of Microsoft Office 2013 32-bit may experience the following behaviour on a 2008R2, 2012 or 2012R2 RDS server: each time a user starts Outlook 2013, a window is briefly shown with the message:

MessageConfiguring Microsoft Office 64-bit Components 2013

The message appears for restricted users and administrators alike, but there's no apparent effect that Outlook is impaired in functionality.

To resolve the matter, you need to install the Windows Search Service role (found under File Services; PS: Search-Service). As soon as this role is installed and its services running, the message will no longer appear. A reboot is not required.

The components it configures are necessary to link t  ...
edited by on January 23rd 2014, at 10:28

The Debugging tools for Windows (a.k.a. Windbg) for Windows 8.1 can still be downloaded separately. Although it's now part of the Windows Driver Kit (WDK), you can still download the Windows 8.1 SDK Installer and select only the debugging tools. It's an about 180MB download (without the symbols).

http://msdn.microsoft.com/en-us/windows/hardware/hh852365

edited by on January 10th 2014, at 13:05

The NETLOGON folder is in fact a subfolder of the SYSVOL directory. Unless this location is changed, you can find it here:

C:\WINDOWS\sysvol\*yourdomain*\scripts

(replace *yourdomain* with the DNS name of your Windows domain)

edited by on January 8th 2014, at 14:34

To allow an Exchange user to send from an external e-mail address, perform the following steps:

  1. Create a Mail Contact with the correct external e-mail address in AD and in Exchange.
  2. Open Exchange Management Shell and set up the permissions:
    Get-MailContact MyUser@MyExternalDomain.com | Add-ADPermission -User MyUser@MyLocalDomain -AccessRights ExtendedRight -ExtendedRights "Send As"
    Replace the first e-mail address with the external one, the second part contains the user you wish to assign the permission to.
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 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 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 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.

showing posts tagged with 'windows'
 
 
« November 2024»
SunMonTueWedThuFriSat
     12
3456789
10111213141516
17181920212223
24252627282930
 
Links
 
Quote
« Debating Windows vs. Linux vs. Mac is pointless: they all have their merits and flaws, and it ultimately comes to down to personal preference. »
Me