Friday, September 7, 2012

iPhone connects to ActiveSync but mail will not download.  Fails to connect to server.



If a user cannot connect to an iPhone use the following work around.

On a Domain Controller, Click on Start/All Programs/Administrative Tools/Active Directory Users and Computers
Click on View and Select Advanced Features

 
 
 
 
 
Select a mailbox that isn’t working with Active Sync, double click on the account, Select the Security Tab and then the Advanced Button.



 
 
 
 
 
 
 
 
Select Exchange Servers, and tick the Include inheritable permissions toggle then Apply and OK.



 
 
 
 
 

Thursday, May 26, 2011

RDWeb no longer seeing my 2nd RD Session Host

Firstly, as this server TS1 seems to be the root cause of the second farm’s problem, please verify if the RDP is working correctly on this server. To check that, please use mstsc /v:TS1 from the Web Server side. If that fails, we can go on troubleshooting on RDP scope.

If the RDC connection works correctly but the Web Access cannot retrieve applications that server, please confirm if the Web Access server has been listed in the TS Web Access Computers local group on the TS1. If not, please add it.

If the server is already listed but the issue persists, please use the following steps on the IDC091T05 server:

1.     Start the WmiMgmt.msc MMC snap-in.
2.     Right-click the WMI Control node, and then click Properties.
3.     Click the Security tab, click Root , click CIMV2 , and then click TerminalService.
4.     Select the TerminalServices node, and click Security .
5.     Click Add, type inside the object name for the "TS Web Access Computers" local security group, and then click OK :

TS1 \ TS Web Access Computers
6.     In the list of the Permission check boxes, click to select the Execute Methods , Enable Account , and Remote Enable check boxes.
7.     Click OK, and then close the Properties dialog box for TerminalServices.

Monday, March 7, 2011

Rebuild or Repair WMI

Rebuilding the WMI Repository

If you experience behavior when using WMI, such as application errors or scripts that used to work are no longer working, you may have a corrupted WMI repository. To fix a corrupted WMI repository, use these steps:

Windows XP and Windows Vista

Click Start, Run and type CMD.EXE
Note: In Windows Vista, you need to open an elevated Command Prompt window. To do so, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
Type this command and press Enter:
net stop winmgmt
Using Windows Explorer, rename the folder %windir%\System32\Wbem\Repository. (For example, %windir%\System32\Wbem\Repository_bad). %windir% represents the path to the Windows directory, which is typically C:\Windows.
Switch to Command Prompt window, and type the following and press ENTER after each line:
net start winmgmt
EXIT
Courtesy: The above is excerpted from Microsoft Technet article WMI Isn't Working!
© 2007 Microsoft Corporation. All rights reserved.

For Windows XP Service Pack 2

Click Start, Run and type the following command:
rundll32 wbemupgd, UpgradeRepository
This command is used to detect and repair a corrupted WMI Repository. The results are stored in the setup.log (%windir%\system32\wbem\logs\setup.log) file.

For Windows Vista

Open an elevated Command Prompt window. To do so, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
Type the following command:
winmgmt  /salvagerepository
The above command Performs a consistency check on the WMI repository, and if an inconsistency is detected, rebuilds the repository. The content of the inconsistent repository is merged into the rebuilt repository, if it can be read.

For Windows Server 2003

Use the following command to detect and repair a corrupted WMI Repository:
rundll32 wbemupgd, RepairWMISetup

Re-registering the WMI components (Ref WMI FAQ)

The .DLL and .EXE files used by WMI are located in %windir%\system32\wbem. You might need to re-register all the .DLL and .EXE files in this directory. If you are running a 64-bit system you might also need to check for .DLLs and .EXE files in %windir%\sysWOW64\wbem.
To re-register the WMI components, run the following commands at the command prompt:
  • cd /d %windir%\system32\wbem
  • for %i in (*.dll) do RegSvr32 -s %i
  • for %i in (*.exe) do %i /RegServer

Note that none of the above two methods restore the missing files related to Windows Management Instrumentation (WMI). So, below is a comprehensive repair procedure that restores all the missing WMI modules. In case of missing WMI modules, you may use the following method.

Comprehensive rebuild method

Important note:  If you've installed a Service Pack, you need to insert your Windows XP CD with Service Pack integration (called as the Slipstreamed Windows XP CD). If you don't have one, you may point to the %Windir%\ServicePackFiles\i386 folder for a recent version of the system files required during WMI repair. Or you may create a slipstreamed Windows XP CD and insert it when prompted.
Click Start, Run and type the following command, and press ENTER:

rundll32.exe setupapi,InstallHinfSection WBEM 132 %windir%\inf\wbemoc.inf

Insert your Windows XP CD into the drive when prompted. Repair process should take few minutes to complete. Then restart Windows for the changes to take effect.

Wednesday, February 23, 2011

Publish standalone RootCA CRL to Issuing CA and Active Directory

On the  RootCA server.
Start Certificate Authority
right click on revoked certificates->all tasks->publish
explore to windir\system32\certsrv\certenroll
copy rootca.crl to file://issuingca/certenroll
switch to issuingca server
start cmd window
certutil -dspublish windir\system32\certsrv\certenroll\rootca.crl

Windows 7 cannot connect to printer 0x0000000a


1. Delete your printer driver

2. Go to Services and turn Print Spooling OFF

3. Count to 10 slowly and turn Print Spooling ON

4. Re-install printer driver.

Wednesday, February 9, 2011

Allow Anonymous relay from specified receive connector in Exchange 2007

Get-ReceiveConnector "Receive Connector Name" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient"

Monday, January 3, 2011

Deploying Hyper-V servers using ConfigMgr 2007 SP2

1. DISM \Mount-Wim /Wimfile:E:\images\myimage.wim /index:1 /Mountdir:C:\MyDir\Mount

2. Inject Hyper-V using Dism
dism /image:C:\MyDir\Mount /Enable-Feature /FeatureName:Microsoft-Hyper-V

3. Commit the changes
DISM /Unmount-Wim /Mountdir:C:\MyDir\Mount /Commit

4. Update the distribution point