Blogs

KACE: Custom Ticket Rule to Prevent Email Loops

Follow these steps to stop email loops from specified email addresses. This is different than the KB article 116088 (https://support.software.dell.com/es-es/k1000-systems-management-appliance/kb/116088) in that 1) you do not have to turn off the "Accept email from unknown users", 2) you can specify a list of email addresses you specifically want to block, 3) it doesn't rely on a time interval to take effect. I needed these options as we have certain emails from unknown users come in occasionally, such as software license renewals, ssl renewals, new hires, other helpdesk systems, etc. This will also work for Out of Office replies if needed if you put the user email in the list.

The way this will work is it sets the submitter to unassigned so that Kace doesn't have an email to send it back to. When Kace receives an email, it will automatically send a confirmation back to the user, unless you have that option turned off. If it is received from an unknown or outside user, Kace will create an account for them when you have the "Accept email from unknown users" option checked. If an email address is listed in this custom ticket rule, once it saves the ticket (which it does on creation), it sets it to Unassigned for the submitter. While the system will send one email out when it creates the ticket, and the end system may send a reply, Kace will not send anything back out again, because the ticket does not have a submitter for it. So, you stop the email loop after one replied email, instead of a timed interval.

WARNING: This will execute an update query on the database. Proceed carefully. You are responsible for damages to the database.

1. Go to Helpdesk>Configuration>Rules

2. Click on Choose Action>New (Wizard)

3. Choose "Ticket Submitter User Name", select "=", and then type the email address you want to block (or anything, for that matter. will be changed later), then Next

4. Choose "Ticket Submitter User Name" again, ("change value to" should be selected), then put a 0 in the change to field. Click Done.

5. On the next screen, you will see the SQL select query. Scroll to the bottom to the where clause. Find the
USER.USER_NAME = 'sample@emaildomain.com' entry.
Change it to
USER.EMAIL RLIKE 'email1@email.com|email2@email.com|email3@email.com' 
The Syntax is important here. USER.EMAIL matches the email account of the submitter. RLIKE matches a regular expression, which in this case is a pipe (|) delimited list (or just one email. thats up to your situation) in single quotes. Do not delete any of the parenthesis. This may break your query.

6. You can preview the tickets it will find before applying the rule by clicking the "View Ticket Search Results" link.

7. Check "Email results" and enter your email if you'd like to be notified when the rule is fired off.

8. Verify the "Run update query" box is checked,  and that it has:

update HD_TICKET, USER as T5
    set HD_TICKET.SUBMITTER_ID = 0
  where
        (HD_TICKET.ID in (<TICKET_IDS>))

In the box. This will set the submitter to "Unassigned", virtually eliminating the reply to address.

9. Set the schedule to "On Ticket Save"

Be the first to comment

Microsoft Outlook Common Errors: Causes and their Solutions

As we all know about Microsoft Outlook (especially professional people) which is an email client developed by Microsoft. In Microsoft Outlook premises error can be raised at any time. To fix such type of issues in MS Outlook, a user must have information regarding the causes of concerned error. Here, in this article, I am going to cover those common causes and their solutions that occurred mostly in MS Outlook.


1Cannot start MS Outlook :

If Microsoft Outlook displays an error: “Cannot start Microsoft Outlook. Cannot open the Outlook window” as shown in given screenshot, then there might be several cause behind appearing this error. Some of them are listed below:

Causes:

  • According to the Microsoft, the main cause of this error is corrupted Navigation pane settings file i.e. profile name.xml. Basically, the profilename.xml is the name your Microsoft Outlook profile. When the size of file becomes 0 KB, it indicates that the file is corrupted.
  • When you are using Microsoft Outlook in compatibility mode, then this error may also come up.
  •  If Microsoft Outlook Data file have been deleted or damaged somehow, then this error might be extended.
KhS77F.png

Solutions:

  • Start MS Outlook in Safe Mode. To do so: Press “Start Key” + “R” >>Type “outlook.exe<space>/safe” in run dialog box.
U5P8SK.png
  •  If Microsoft Outlook opens in safe mode, then remove add-ins by Clicking on the “File” tab >> “Options” >> “Add-Ins”>> Select “Com Add-ins” and click on “Go”  >> Clear all check boxes in the list & click “OK” button >> Restart “Microsoft Outlook” (normally, not in safe mode).
NjjEVQ.png
Rn5DxQ.png
  • You can also create a new user profile in MS Outlook.
  • Even after creating a new user profile, if the problem remains same, then reset the navigation pane. To do so: Press “Window Key” + “R” >>Type “outlook.exe<space>/resetnavpane” in run dialog box.
F9abLH.png
  • Last but not the least, give a try to “SCANPST.EXE (Inbox Repair Tool”), which is a free (inbuilt) utility developed by Microsoft.
2. Microsoft Outlook takes too much time to load:

There might be many reasons that induce conflicts in Outlook and makes it slow. Here, in this section I am going to discuss some of those causes, which generally turn down the performance of Outlook.

Causes:

  • Outlook users generally pick some add-ins to make outlook more feasible or can say speed up the various task, but unknowingly they called detrimental plug-ins, which does not prove much instrumental as in concerned manner they were added. As a result, such vile plug-ins increases the loading time of Outlook.
  • Supposedly, hefty Outlook Data file or when Outlook outruns by its default size, then Outlook starts mitigating the Outlook performance.

Solution:

  • First of all, disable the Add-Ins. To do so, you can see the procedure above for disabling the Add-ins in MS Outlook.
  • Archive your over sized Outlook Data File. Remember, Archiving features in MS Outlook will take too much time, if the Outlook PST File is too large. As we all know that, nowadays most of the professional people have less time to spend on look over data. So, they can go with the any Split PST Tool to break their large Outlook Data File into smaller PST’s by Folder, Size, Date and Year.

3. Microsoft Outlook Unable to send Emails after upgrading from Window 8, 8.1 to Window 10:

To overcome this issue, you should run “SFC (System File Checker)”in command prompt:

To do so:

  • Type “Command Prompt” in search bar >> a command prompt icon will be shown to you, right click on it and select “Run as administrator” (look in screenshot).
zGy5Bt.png
  • Type “sfc<space>/scannow” in the command prompt. Wait until the process does not complete.
AxSmUU.png
  •   Now, reboot your system.

Noteworthy thing: http://sysc.org/discuss/unable-send-emails-outlook-upgrading-windows-10/

4. Microsoft Outlook gets freeze or Hang/Outlook Not Responding:

Most of the time this error appears when you send any email or open a file in Microsoft Outlook 2010 or Microsoft Outlook 2013. The error appears like this:

Causes:

  • Microsoft Outlook is in use by another process.
  •  Enabling of Add-Ins in access.
  • Corruption Outlook Profile.
  • Large Outlook Mailbox.
  • Corrupted or damaged Microsoft Outlook Data File.

Solutions:

  • The best solution which most of the time works is removing Outlook from Task Manager (In simple term, turning down Outlook using task manager). To do so: Press “Ctrl +Shift + Delete” (Combination) >> Go to “Task Manager” >> Select “Microsoft Outlook”>> click on “End Task”.
wYdHVc.png
  • Try to open MS Outlook in safe mode.
  • Remove MS Outlook Add-ins.
  • Repair Outlook Data File.
  • Disable your antivirus Programs.
  • Reduce the size of Mailbox and Outlook PST File by using Compact Now Feature in MS Outlook.
  • Disable Hardware Graphics acceleration.
  • Use Microsoft Fix It Tool.
5. Microsoft Outlook error 0x800CCC0F:

Among all errors, MS Outlook error 0x800CCC0F is a staple problem and usually appears when you tried to send or receive emails in Microsoft Outlook. The Outlook shows the error message something like this: “Sending reported error (0X800CCC0F): "The connection to the server was interrupted" as shown in screenshot at the time of bug. Have a look at the main causes and solutions to fix the Outlook error 0x800CCC0F.

muEex0.png

Causes:

  •  MS Outlook error code 0x800CCC0F typically appears, when your antivirus program enabled in MS Outlook or its settings is relatively not analogous to Outlook.
  • Blocked advanced settings by ISP.
  • The Outlook error 0x800CCC0F may also appear when Microsoft Windows Firewall blocks MS Outlook.

Solutions:

  • Make sure that you are connected with Internet.To resolve this error, disable your antivirus program as well as Windows Firewall. Know how to disable Windows Firewall. Please follow the path: Press “Start” Key + “R” >> Type “Control Panel”& click on “OK” button >> click on “Network and sharing Center” >> Click on “Windows Firewall” (See bottom-left) >> Click on “Turn Windows Firewall on or off” >> a new window will open click on “Turn off Windows Firewall (not recommended)” for both Private and Public network settings.
Note:  These above steps that I defined are for MS Outlook 2010.

  • Make sure that Outgoing Server (SMTP) port is 25 and Incoming Server (POP3) port is 110 by default. To check it: Open "MS Outlook" >> Click on “File” Tab >> “Account Settings” >> “Account Settings” >> Click twice on your email account >> “More Settings” >> “Advanced” Tab.
AxsDd5.png
  • If the above solutions unable to fix the issue, then it can be the issue of corrupted or damaged Outlook PST File. To repair minor level corruption in PST file, you should try to run SCANPST.EXE (Inbox Repair Tool) which is free tool developed by Microsoft. Sometimes, this tool fails to repair Outlook PST File just because it has has not developed to face highly corrupted PST File bugs. So, in such a scenario, you must need a commercial Outlook PST Repair Tool to repair highly corrupted Outlook Data.
6. Outlook PST File is not a personal Folder File.
There might be several reasons of appearing this error: “Outlook.pst is not a personal folders file”. Here, in this section, I am going to discuss some of the causes and their solutions to get over this error.

0NzyLS.gif

Causes:

  • If your Outlook Data File is on CD/DVD or marked as “Read only” attribute, then in such a case this error will appear.
  • This message also appears when you import or restore corrupted Outlook PST File or split PST file into MS Outlook.
  • This error might be appearing if MS Outlook is running and randomly System shutdowns happen due to power failure. 

Solutions:

  • First, you have to copy Outlook PST File from the CD/DVD and paste on your local hard drive.I would like to suggest you to make a sub-folder named as “Outlook” of your Document Folder and put that PST file in Outlook Folder. After doing this, uncheck the attribute “Read Only” , if checked, To do so : Right Click on "PST" File >> Go to "Properties" >> Deselect the option: “Read Only”.
Fk67pM.png

Note: Make sure that did not overwrite any existing Outlook Data File.

  • Do not import Outlook Data File, once you have restored the PST File by above method.
  • Proper way to open Outlook PST File: Click on "File" Tab >> "Open" >> "Open Outlook Data File".
  • Close MS Outlook and Repair Outlook Data File by Using "Scanpst.exe (Inbox Repair Tool)" which is a free utility developed by Microsoft.


Be the first to comment

KACE K1000 Script to uninstall all versions of iTunes

I discovered that the K1000 msi configuration policy uninstaller fails to work for iTunes version 12 (it worked for 11, why it no longer works, I don't know).
When I ran the script created by the policy, it ran successfully (so it said), but inventory showed iTunes still installed. Bummer.
So I turned to the old standby, VBScript to uninstall it.
Here it is if anyone needs it:
On Error Resume Next
Const HKEY_LOCAL_MACHINE = &H80000002
strComputer = "."
Set WshShell = CreateObject("wscript.Shell")

Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" &_
strComputer & "\root\default:StdRegProv")

strKeyPath = "SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall"
oReg.EnumKey HKEY_LOCAL_MACHINE, strKeyPath, arrSubKeys

For Each subkey In arrSubKeys
strDisplayName = WshShell.RegRead ("HKLM\" & strKeyPath & "\" & subkey & "\DisplayName")
If strDisplayName = "iTunes" Then
WshShell.Run "msiexec.exe /X " & SubKey & " /qn", 7, True
End If
Next

Be the first to comment

What is “System File Checker Tool” or “sfc”?

System file checker is a windows system utility that permits users to repair and restore the Windows system files. This is embedded in all Windows NT series operating systems. System file checker is a command line utility for all Windows operating systems series. The sfc.exe checks specific folder path including boot folders and windows folders. SFC is the integral part of Windows system protection.

If tool finds any problem, it tries to replace the error files from DLL Cache. If the file is not found in the DLL Cache or if the Cache is corrupted, the user needs to provide the network installation path or any Windows installation media. Let’s see how to run the tool and fix the system file issues using it.

Note: System File Checker solves the issue in most of the cases. When MS Outlook Unable to send emails after upgrading the Window 10 and also sometimes Sending reported 0x800CCC13 occurs.

How to run sfc.exe?

sfc.exe is a simple command which can be executed from Command prompt of the Windows Operating System. The command is as follows:

  • sfc/<space>scannow

Steps to run sfc.exe tool

  1.  Run command prompt with administrative privilege. For this do: Start >> cmd >> right click on it and then select “Run as Administrator
  2. After opening command prompt execute the command ‘sfc/scannow’.

nXd1v6.png

 TIP: Do not exit command prompt until the scanning is completed fully.

This command scans all protected system files and replaces corrupted ones with cached copy. The cached copy of the files will be located in a compressed folder at: %WinDir%\System32\dllcache

 ®     ‘%WinDir%’ is the placeholder for the Windows operating system folders.

The four possible output conditions for sfc.exe execution are

  • WRP doesn’t fine any integrity violations so that the system files are in healthy condition.
  • WRP is unable to perform the requested action, this can happen if PendingRenames or PendingDeletes folders exist under temp files.1RFI5G.png
  • WRP successfully repaired the corrupted files and the details are included in CBS.Log files.buFzXr.png
  • WRP is unable to repair the corrupted system files and the details exist in CBS.Log files.cUexJE.png

How to View and analyze the CBS.log file?

The contents from this log file can be copied to text file to analyze the corrupted file details. The extraction of the contents from log file to txt file can be carried out using Findstr command. For this operation open command prompt and execute the following:

pJBI6s.png

This command copies the content of the CBS log file to a new text file named sfc_contents.txt on desktop. So that user can easily read the contents using any text editors. This file contains date time and other SFC details. One can view and analyze the details obtained by executing the sfc.exe tool.

Is there any solution to replace the corrupted files?

Let’s see if there exists any solution to repair the corrupted system files where the SFC tool failed.  One possible solution is to replace the corrupted file with known good copy from other system running the same OS as that of yours. Let’s see how to carry out this task.

1.First take the administrative privilege from the damaged file. To do this Open command prompt, then execute: takeown /f FileNameWithPath
2.To grant admins full access  to the file execute the following query: icacls FileNameWithPath /GRANT ADMINISTRATORS:F
3.To replace the damaged file with healthy file do: Copy SourceFilePath DestinationPath

Conclusion

The article described about how to recover corrupted Windows System Files using System file Checker Tool. The tool is capable of fixing all types of files corruptions. This is as free command line utility from Microsoft and can be used by anyone to fix the stem file errors. The tool automatically replaces the corrupted system files from DLL cache file.

Be the first to comment

KACE: Silent removal of unresponsive Kace agents

When Kace agents become unresponsive, due to eg hibernation of the laptop are broken configuration it needs to be uninstalled.

 

Here is a tool to silently uninstall agents from multiple computers at once over the network with no user notifications or user interaction.
The computers need to be connected to the network.

 

The script uses the PSexec util found on https://technet.microsoft.com/en-us/sysinternals/bb897553.aspx

PsExec is a light-weight telnet-replacement that lets you execute processes on other systems, complete with full interactivity for console applications, without having to manually install client software. PsExec's most powerful uses include launching interactive command-prompts on remote systems and remote-enabling tools like IpConfig that otherwise do not have the ability to show information about remote systems.

Note: some anti-virus scanners report that one or more of the tools are infected with a "remote admin" virus. None of the PsTools contain viruses, but they have been used by viruses, which is why they trigger virus notifications.

Installation: Save PsExec to a folder of your choice.  For me it's c:\temp Just be sure to adjust the command accordingly if you place PSexec somewhere else.
note: Typing "psexec" displays its usage syntax.

 

Script requisites

1. Computer list
create a text file called computerlist.txt, and type all computer names needing the Kace agent removal in there.  Should you want to use IP addresses instead of machine names, that is no problem  

save this file in the same location as your PSexec.exe file

2. Removal script
create a bat file called ampuninstall.bat and add the following 2 lines      

cd C:\Program Files\dell\kace
AMPTools uninstall all
 

save this batch file in the same location as your PSexec.exe file and the computerlist.txt
 

IMPORTANT - this is for x86 computers
in case of x64 computers be sure to change the program files folder location

cd C:\Program Files (x86)\dell\kace
AMPTools uninstall all
 

save this batch file in the same location as your PSexec.exe file and the computerlist.txt

 

note: see https://support.software.dell.com/k1000-systems-management-appliance/kb/146458 for more AMPTools command switches


3. Script

for /f %G in ('type "c:\temp\computerlist.txt"') do psexec \\%G -s -c -accepteula ampuninstall.bat

 

run the script by opening a command prompt and browse to your folder where PSexec is placed into - for me it's c:\temp.
should you use a different location, be sure to to adjust the command accordingly. 
 

explanation of the script

-s = run as local system
-c = copy file (ampuninstall.bat) over to client and then execute
-accepteula = not to show the popup to accept the use of PSexec


Essentially what this command does is sets a variable for the machine name, and for every line in the computerlist.txt file, replaces that variable (%G) with the target IP or hostname you want to connect to.
Whenever the script can't connect to a computer it will skip and move on to the next one in the list

 

Sources - combination of these 2 Kace KB's and a lot of sweat and testing
https://support.software.dell.com/k1000-systems-management-appliance/kb/146458
https://support.software.dell.com/kb/127898    

 

Agent reinstallation

Once successfully removed, the Kace agent will reinstall itself from GPO.

Be the first to comment
Showing 1 - 5 of 2788 results