Tag: Microsoft

[Solved] DefaultThrottlingPolicy has gone over budget ‘xxx’ times for component ‘RCA’ within a one minute period – Event log

 In Exchange Server 2010 SP1, client throttling policies are used to manage the performance of the Exchange organization.  All client throttling policies are enabled by default i in Exchange Server 2010 SP1. The throttling policy has group settings that control the amount of resources that a user or a connection can use.

Throttling Policy settings are only applicable for Exchange Server 2010 SP1 and later. If the application event log on the Exchange or SBS2011 servers displays an error message similar to the following example, then the throttling policy settings are applicable to your system:

Process Microsoft.Exchange.RpcClientAccess.Service.exe (PID=XXXX). User ‘Sid~ServiceAccount~RCA~false’ has gone over budget ‘XXX’ times for component ‘RCA’ within a one minute period. Info: Policy:DefaultThrottlingPolicy_abcdefghijklmnopqrstuvwxyz, Parts:ABC:XXX;’. Threshold value: ‘110’

 

If you are experiencing slow Exchange email ingestion that may be caused by these policies, you can modify client throttling policy for an archive service account.

Complete the following steps:

  1. Create the throttling policy: on a computer that hosts the Microsoft Exchange Management Shell, open the Microsoft Exchange Management Shell. Enter the following:

    New-ThrottlingPolicy My_New_Policy

  2. Configure the throttling policy by entering the following:

    Set-ThrottlingPolicy My_New_Policy -RCAMaxConcurrency 150

  3. Apply the throttling policy to archive service account by entering the following:

    Set-Mailbox “MyUserName” -ThrottlingPolicy My_New_Policy

The My_New_Policy can be any name you want to call policy, The My_UserName is the mail box name of the person or account you want to add to the new  ploicy.

 

 

How to force the Offline address book to update in Microsoft Outlook

 

How to force the address book to update
When a new email account is created in Exchange it will not normally appear in the address book of others until the following day. This procedure shows how to force newly created accounts to be visible in the address book:

1.Force an address list update on the Exchange server
2.Pull down the address list in Outlook.

Force an address list update on the Exchange server
1.On the server running Exchange, open Exchange System Manager.
2.Expand “Recipients”.
3.Select “Offline Address Lists”
In the default configuration there will only be one offline address list shown in the right hand pane – “Default Offline Address List”. If other address lists have been created then they will also be listed.
4.Right click the address list to update (typically “Default Offline Address List”) and select “Rebuild”

A message will be shown warning that this may take a long time depending on the number of recipients in the domain. Allow it to rebuild the offline address list.
Pull down the address list in Outlook
This needs to be done on each pc running outlook which requires the latest address book:

1.Start up Outlook.
2.Tools → Send/Receive → Download Address Book…
3.On the “Offline Address Book” dialog click [OK]

 

Enjoy

App Assure – Replay Core Mountability check for ‘Mailbox Database’ failed: Exchange database engine error: Error closing database

App Asure Replay CoreWith App Assure you may get the following errors after a new install of a Replay Core server and an the agent running on a Exchange 2010 server database.

Error

Thread: 2520

Logger: DsmRpChecker

Context:

Source Location: DsmRecoveryPointChecker.cpp:341

Details:

Mountability check for ‘Mailbox Database 0401075076’ failed: Exchange database engine error: Error closing database

and/or

Error

Thread: 2520

Logger: DsmRpChecker

Context:

Source Location: DsmRecoveryPointChecker.cpp:341

Details:

Mountability check for ‘Mailbox Database 0401075076’ failed: Exchange database engine error: Unable to initialize JET session. See log for details.

 

There is a known issue with Exchange 2010 running on SP1 with RollUps where this problem is experienced.

Please apply the below registry fix to the Replay Core server, and capture a new recovery point (snapshot) from the protected server to resolve the issue. Furthermore, after deployment of this fix you can go back and check the past recovery points that failed and “Force Recovery Point Check” to confirm they are good as well and get the green check symbol assigned to them.

Modify the registry on the Replay Core at the following location and assigned the specified value below:

Navigate to the location: HKEY_LOCAL_MACHINE\SOFTWARE\AppAssure\ReplayDSM\EseConfig

Modify value for “ForceDeleteUnicodeIndex” (type REG_DWORD) and assign a value of 2.

 

I hope this helps some one out there..

Enjoy 😎

Cubert

[Solved] A problem prevented Customer Experience Improvement Program data from being sent to Microsoft, (Error 80004005).

 

Customer Experience Improvement Program data fails to upload.

This alert is generated when a failure to upload the CEIP data to Microsoft fails on servers where you opted to be included in the CEIP. This is usually a firewall issue but sometimes admins may also have inatvertantly select to be included and really don’t want to be. To fix this or really turn it off you will find the task in the Task Scheduler under the Customer Experience Improvement Program.

 

1.Click Start, point to Administrative Tools, and then click Task Scheduler.
2.In the tree pane, open Task Scheduler Library, open Microsoft, open Windows, and then select Customer Experience Improvement Program.
3.In the results pane, Right Click the Uploader task and select to disable.

This will prevent the task from running and stop any more alerts.

Enjoy

 

Cubert

[Kaseya Script] Modify/Disable TCP Global Parameters on Windows systems

Need another Kaseya agent procedure? Here is one I use alot.

This article describes the TCP Chimney Offload, Receive Side Scaling (RSS), and Network Direct Memory Access (NetDMA) and other features that are available for the TCP/IP protocol inside of Windows. I have spent probably hundreds of hours on cases involving TCP Offloading and I know most of the signs (intermittent dropped connections, missing traffic in network traces, RDP blank windows, etc…).

I created a Kaseya script that goes and disables many of these NIC features Windows puts in their OS that causes so much havoc at times. 

Download Script here -> Procedure_Network_feature_shutdown

It is pretty basic, it sets several registery values and runs several shell CMDs using netsh to disable these protocols.

I hope this helps some of you out there.

Cubert.

[Kaseya Scripts] Repair VSS Writers on Windows Servers Agent Procedure

Are you having VSS issues?  Need a script to launch when either errors are reported or as a point and shoot script to repair VSS writer issues? Well Cubert has created a new VSS script that is fairly simple in nature but gets the job done nicely. This Kasey Agent Procedure was written for Kaseya 6+ RMM and has 2 parts.

Part 1: Is the VSS-RESET.bat  batch file that does the actual work by shutting down the services and re-registering the dlls used by the different VSS Writers. Afterwards it outputs a  file to the temp directory with a printout of the VSS writer list cmd.

Part 2: Is the Kaseya Agent procedure that copies the batch file to the system and executes it. It then waits a few minutes for everything to complete and then grabs the report file generated by the batch file and places it on the “GetFile” tab under your [Agent data] menu item inside of LiveConnect.

You can review the report file to see if you are still generating errors after the repairs are preformed.

Download Agent Procedure here -> VSS-RESET

I hope this helps someone out there is Kaseya land!

Cubert.

[Kaseya Agent Procedure] – Run CHKDSK And Repair If Needed.

Free Kaseya Script – Run CHKDSK And Repair

Here is another free script from Cubert’s Dwelling, An Agent procedure that will run a CHKDSK in read only mode. Parse the output and run a chkdsk /F if it meets the criteria set forth in the script. It then emails an alert with the scan results to a email address provided before it uploads a copy of the scan to the get file for storage and review. Finally it updates 2 custom fields in the system info table with a brief result and the last run time. If it finds the disk healthy it will report as such if not it will report one of several error types.

Download Script Here

You will need to unzip the script and import it into Kaseya. Once imported edit the script and find the 2 places it email out and update the email address(es), Then you will need to add the 2 custom fields into your System-info table.

To add the custom fields:
1#  Open Kaseya and go to [Audit] – [View Individual Data] – [System Information] and select the button marked [New Custom Field]

2# The next box that pops up will create a new field, We will need to add 2 fields the first is CheckDisk Status and it will be a type String and Check Disk Updated with a type String.

Now run your disk check and see what it shows. If it meets with the right disk errors, a  repair is sent to the system and a email to you to reboot system when you can so the repair can complete. You can add another execute command under where we call the chkdsk /F with a shutdown -r -t 3 and that will cause the system to reboot its self after issuing the fix cmd. This is great for servers where your scheduling the disk scans during maintenance cycles but not so good with workstations where user gets booted up then a scan runs that then reboots the system will only inflame your users. So be mindful of how you use a shutdown cmd.

Enjoy

Cubert 🙂

[Solved]-Windows Easy Transfer Won’t Connect Between Systems Across The Network

How to get your Windows Easy Transfer to work over the Network.

This is a very common issue, I seem to hit the never ending “Trying to Connect” cycle of death on just about every other time I use Windows Easy Transfer. It doesn’t matter if your doing a transfer from XP to 7 or from 7 to 7, I’ve seen it time and time again.

I foung the Quick fix that works everytime I’ve used it.

The Guys over at LSP-Fix have a simple little program that fixes winsock issues.

LSP-Fix is a free Windows utility to repair a loss of Internet access associated with certain types of software. This type of software, known as a Layered Service Provider or LSP, typically handles low-level Internet-related tasks, and data is passed through a chain of these programs on its way to and from the Internet. However, due to bugs in the LSP software or deletion of the software, this chain can get broken, causing the Internet connection to become inaccessible or just a wee bit unstable. 

Download LSP-Fix here.

I know it doesn’t seem plausible that your winsock is messed up but take it from me, New Laptops out of the box can and will have issues. Download and run the tool and it will corrected the issues and your copy will start working.

LSP-Fix does not delete anything, it only fixes the order of the LSP’s. It does not require a reboot after you run the tool, just run the tool, select fix and then restart your Windows Easy Transfer process. I would suggest that you run it on both the sending and receiving systems, I find that they all seem to need  reording.

I hope this helps someon out there.

Cubert

How-to Create a SMTP Relay Connector for Microsoft Exchange Server 2010 using PowerShell

Create new connector and assign relay permissions.

Pretty simple really,

Open your exchange power shell and enter the following cmds to create and set permissions on your new connector. Use the New-ReceiveConnectorcmdlet to create the Receive connector Anonymous Relay that listens on local IP addresses.

New-ReceiveConnector -Name “Anonymous Relay” -Usage Custom -PermissionGroups AnonymousUsers -Bindings 192.168.1.5:25 -RemoteIpRanges 192.168.1.1-192.168.1.255

 

Now we must use the Exchange Shell to grant relay permission to anonymous connections on the new Receive connector.  The next cmd-let retrieves the specified Receive connector information and pipes the result to the Add-ADPermissioncmdlet to grant relay permission to anonymous connections on the new Receive connector.

Get-ReceiveConnector “Anonymous Relay” | Add-ADPermission -User “NT AUTHORITY\ANONYMOUS LOGON” -ExtendedRights “Ms-Exch-SMTP-Accept-Any-Recipient”

You can open up a telnet session to the IP of your exchange server and test the mail flow. This will confirm that your relay is up and running.

 

The first thing to do is to open a connection from your computer to your mail server.
telnet 192.168.1.5 25
You should receive a reply like:
Trying ???.???.???.???…
Connected to 192.168.1.5
Escape character is ‘^]’.
220 mail.domain.ext Microsoft Exchange Server XXX.YYY.xxx.yyy

You will then need to delcare where you are sending the email from:
HELO local.domain.name – dont worry too much about your local domain name.

This should give you:
250 192.168.1.5 Hello local.domain.name [Your IP address],

Now give your email address:
MAIL FROM:< mail@domain.com >

Should yeild:
250 2.1.0 mail@domain.com... Sender ok

Now give the recipients address:
RCPT TO:< mail@otherdomain.com >

Should yeild:
250 2.1.0 mail@otherdomain.com... Recipient ok

To start composing the message issue the command DATA

If you want a subject for your email type

Subject: type your subject here
You may now proceed to type the body of your message.

To tell the mail server that you have completed the message enter a single “.” on a line on it’s own.
The mail server should reply with: 250 2.0.0 ???????? Message accepted for delivery

You can close the connection by issuing the QUIT command.
The mailserver should reply with something like:

221 2.0.0 mail.domain.com closing connection Connection closed by foreign host.

Enjoy,

Cubert

[Solved]-Remote Web Workplace will not connect to my computer.

You have a user that has a  Home  (Windows 7 Home) or Work (Windows 7 Pro) Computer

When using remote web workplace they selects connect to my computer, picks their computer from the list and then it never makes it past this point. There is a error icon displayed in the lower progress bar area of the browser.

Running IE as a administrator they are able to use RWW just fine.

The user is an administrator on the computer. IE9 has been removed and replaced with IE8 same results.

Windows firewall is off,  We have tried with the firewall on and off, makes no difference.  We have added RWW site to the trusted site and relaxed all the active security settings for the trusted site, same result. The browser add-ons show the Microsoft rdp active control is installed when in IE both as an admin and just launching it normally so what could be hanging us up?

Well you will find that your UAC is on and one of the results of this being active is that Active X functions are suppressed. Just turn off UAC and the problem will go away.

Go to your start button and in the search window type “UAC”. It will launch the UAC Control and allow you to change the settings

Enjoy

Cubert.