the-exe.org just another blog » Tech http://blog.the-exe.org why me? Mon, 05 Jul 2010 21:49:53 +0000 en hourly 1 http://wordpress.org/?v=3.0.1 Check if your CPU supports 64Bit http://blog.the-exe.org/check-if-your-cpu-supports-64bit/ http://blog.the-exe.org/check-if-your-cpu-supports-64bit/#comments Fri, 18 Jun 2010 09:19:10 +0000 eXe http://blog.the-exe.org/?p=869 What to do if you have to check if a remote system that’s running with 32Bit Windows would also support 64Bit?
The easiest way to do this is to download the application CPU-Z, this freeware application works on various windows based systems, even on server systems.
The application will then read out the informations on your CPU and you can see if the CPU supports EM64T.
Check the Link for further Informations and Download.

]]> http://blog.the-exe.org/check-if-your-cpu-supports-64bit/feed/ 0 Error installing Update KB974417 http://blog.the-exe.org/error-installing-update-kb974417/ http://blog.the-exe.org/error-installing-update-kb974417/#comments Wed, 28 Apr 2010 14:16:04 +0000 eXe http://blog.the-exe.org/?p=851 Symptom: On Windows XP machine update KB974417 cannot be installed and fails with the warning that it does not apply to any installed product.
Problem: There is another update that blocks the installation.
Solution: Uninstall Update KB976569 in add and remove software. You will find the update when showing updates in the list under .NET Framework 2.0 Service Pack 2. After uninstalling, you’ll have to reboot the computer. Install the KB974417 before reinstalling KB976569. In the end both updates will be installed.
Link to original article: Here

]]> http://blog.the-exe.org/error-installing-update-kb974417/feed/ 0 Disable Windows Firewall via GPO http://blog.the-exe.org/disable-windows-firewall-via-gpo/ http://blog.the-exe.org/disable-windows-firewall-via-gpo/#comments Mon, 26 Apr 2010 06:41:24 +0000 eXe http://blog.the-exe.org/?p=849 Problem: All clients in the network have windows firewall enabled. This may cause problems with the anti-virus to update the clients.
Solution: Disable all firewall services on the clients.
HowTo: Create a GPO that disables every computers windows firewall. You can find an article describing exactly how to do so can be found here.
Additional Info: By doing the stuff described in the link above, the service of the windows firewall is still running. You’ll have to deactivate the service via GPO as well. To do so, go to the group policy editor and ad the following entry: Computer Configuration\Control Panel Settings\Services. Add an entry for the windows firewall service. If your clients use windows XP you have to add an entry for a service called SharedAccess Start type should be set to Disabled. You might also configure to stop the service if it’s still running. If your clients are using windows 7 the service name would be MpsSvc.

]]> http://blog.the-exe.org/disable-windows-firewall-via-gpo/feed/ 0 sage50 and Windows 7 http://blog.the-exe.org/sage50-and-windows-7/ http://blog.the-exe.org/sage50-and-windows-7/#comments Mon, 12 Apr 2010 14:00:50 +0000 eXe http://blog.the-exe.org/?p=845 Problem: sage50 installation fails on Windows 7
Reason: If you start the setup.exe on the DVD, the installation starts with the installation of pervasive database engine before installing sage50.
Solution: Go to the DVD, copy the complete pervasive directory to you local disc. Search the directory for a file called ptksetup.ini then search for the following row:

;PVSW_PSQL_INSTALL_XIO=1

replace 1 by 0 and remove the semicolon in front

PVSW_PSQL_INSTALL_XIO=0

then run the Installation of the pervasive database server out of the directory that you copied earlier.
after the installation is finished, go to the DVD again and start setup.exe. The installation will then work and the program can be used without any problems.

Have fun!

]]> http://blog.the-exe.org/sage50-and-windows-7/feed/ 0 Server Performance Windows Server 2008 (Websites / RDP) http://blog.the-exe.org/server-performance-windows-server-2008-websites-rdp/ http://blog.the-exe.org/server-performance-windows-server-2008-websites-rdp/#comments Thu, 11 Mar 2010 07:58:06 +0000 eXe http://blog.the-exe.org/?p=840 Problem: If you have a web-server with Server 2008 as operating system, you may experience very slow connections to the hosted website and errors in rdp sessions saying that there was a protocol error.
Reason: In Server 2008 IPv6 is enabled by default. This may lead to connection problems and unavailability of hosted services from other systems.
Solution: To solve these problems disable IPv6 on the server.
Attention: If you just uncheck the IPv6 check-box on your network card, you do not disable IPv6. To do so open registry go to the following hive HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\. There should be a key called “DisabledComponents” if so change it’s value to “FF” in hex. If it does not exist, create a new DWORD Key with the value “FF” After you did so, reboot the server and check if the performace has increased.

Source: Microsoft KB Article

]]> http://blog.the-exe.org/server-performance-windows-server-2008-websites-rdp/feed/ 4 Migrating Norman NVC to Norman NEM Exchange Information Store not starting http://blog.the-exe.org/migrating-norman-nvc-to-norman-nem-exchange-information-store-not-starting/ http://blog.the-exe.org/migrating-norman-nvc-to-norman-nem-exchange-information-store-not-starting/#comments Fri, 19 Feb 2010 09:19:48 +0000 eXe http://blog.the-exe.org/?p=835 Symptom: After updating NVC to NEM the Exchange IS is not starting
Problem:The NVC had a flag set if the NVC was on the same server as Exchange. If this flag is set and NVC is no longer available, Exchange cannot start the informationstore.
SolutionTo fix this issue, go to the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\VirusScan

Change the value from 1 to the following:

Key: Enabled
Type: REG_DWORD
Value: 0

]]> http://blog.the-exe.org/migrating-norman-nvc-to-norman-nem-exchange-information-store-not-starting/feed/ 0 Network Drives not connected on Windows Vista in 2008 Domain http://blog.the-exe.org/network-drives-not-connected-on-windows-vista-in-2008-domain/ http://blog.the-exe.org/network-drives-not-connected-on-windows-vista-in-2008-domain/#comments Fri, 08 Jan 2010 09:49:07 +0000 eXe http://blog.the-exe.org/?p=829 I happend to see a Windows Vista Business PC fully patched that could not connect the network drives via GPO from 2008 domain. Group Policy Preference Client Side Extensions for Windows Vista (KB943729) patch was installed on the client. But still no network drives were mapped to the client.

In the eventlog of the client the following entry is created

Log Name: Application
Source: Group Policy Folders
Date: Date
Event ID: 4099
Task Category: (2)
Level: Warning
Keywords: Classic
User: SYSTEM
Computer: Computer Name
Description:
The client-side extension could not log RSoP data because it failed with error code ”0x8004401e This is not a valid MOF file”.

The reason is that the drive mapping ist not working if the following condition is true.

The user that you want the network drives to connect, is member of the local administrators group and the UAC feature of Windows Vista is turned on.

To resolve this issue you’ll have to do one of the following things:

1. remove the user from local admin group
2. disable UAC
3. Add an entry to the client registry as described in the following KB article: KB937624

After doing one of these steps you should do a reboot or gpupdate /force for the changes to apply.

]]> http://blog.the-exe.org/network-drives-not-connected-on-windows-vista-in-2008-domain/feed/ 0 Norman Endpoint Protection: Remote installation not initialized http://blog.the-exe.org/norman-endpoint-protection-remote-installation-not-initialized/ http://blog.the-exe.org/norman-endpoint-protection-remote-installation-not-initialized/#comments Tue, 29 Dec 2009 07:54:16 +0000 eXe http://blog.the-exe.org/?p=821 Since Norman released their latest security Product a few weeks ago, I had several problems when deploying client files from Norman Endpoint Manager to another Server.

After initializing the Push Installation on the Endpoint Manager, Zanda.exe and zlh.exe appear on the remote Server. But even after a few minutes there was no change of it’s state. The zlh.exe process is beeing closed and zanda.exe does not seem to be working anymore.

In fact Norman has a built in delay to start finalizing the installation. This delay should be set to 15 minutes by default, so the network is not blocked by the high load generated when distributing files. If you want to see if zanda is still working, open the eLogger.exe. You can find it in your Norman directory in the subfolder \Npm\Bin\ if you start the eLogger.exe you will see what Zanda is doing.

If you want to immediately start zanda to update, open a command line prompt and enter the following command:

zanda /updatenow

zanda will update now and you will see the information in the eLogger window. If the update is over, you will get the message in eLogger. Then it might take some time for zanda to start the norman services.

All the above information can be found in the norman support issue archive.

Link to original article: here

]]> http://blog.the-exe.org/norman-endpoint-protection-remote-installation-not-initialized/feed/ 0 Backup Exec 12.5 – Error E00002FE http://blog.the-exe.org/backup-exec-12-5-error-e00002fe/ http://blog.the-exe.org/backup-exec-12-5-error-e00002fe/#comments Fri, 02 Oct 2009 06:22:22 +0000 eXe http://blog.the-exe.org/?p=806 Lately I expected an error E00002FE on Backup Exec 12.5 installed on Server 2008. The error which was reported in the Job Log, was the following:

Final error: 0xe00002fe – Cannot log on to MAPI with the specified credentials. Review the resource credentials for the job, and then run the job again.

If you test the credentials in the Job properties, it will give you a successful anyway.

The error happens because the ressources are not in the correct order. By default Backup Exec does the backup for Disks and System State befor saving the Exchange Server. On a server 2008 based server with exchange 2007 installed this will end the backup with an error.

The solution for the event is quite easy if you find the correct page in the symantec backup exec support forum. If you search in the knowledgebase of symantec, you’ll find the following page. http://seer.entsupport.symantec.com/docs/311718.htm On this page a few possible reasons for the problem are listed. If you go down to reason 6 you will find a short note saying this could happen on an 2008 based system with the information store not in te first position of the selections list.

The Link provided in the article (http://seer.entsupport.symantec.com/docs/306830.htm) will bring you to the solution of the problem. Just select the first storage group and move it to the first position on the backup List. If you use public folders move the second storage group to the top position as suggested in the article.

The next time you run the backup job it should finish correctly.

Easy solution for a stupid problem!
Have fun with it

]]> http://blog.the-exe.org/backup-exec-12-5-error-e00002fe/feed/ 0 Restore Deleted Content in Public Folders on Exchange 2007 http://blog.the-exe.org/restore-deleted-content-in-public-folders-on-exchange-2007/ http://blog.the-exe.org/restore-deleted-content-in-public-folders-on-exchange-2007/#comments Thu, 01 Oct 2009 16:55:01 +0000 eXe http://blog.the-exe.org/?p=804 What to do if you, some user or an application deleted content on your public folders in exchange 2007? There are (at least) three possible solutions to solve this issue.
1st solution: run as fast as you can and never come back!
2nd solution: you restore last nights backup and pray to the mighty lord that this works and does not kill the rest of your exchange server
or you just restore the deleted items by using the
3rd solution: dowload the PFDAVAdmin tool from Microsofts website. Start the application, connect to your exchange server with an account that has sufficient rights to access the public folder in which the items were before beeing deleted. Then click the Public Folders on the Left and navigate tot the directory in which you want to restore the items. After selecting the folder, click on Items on the right side of the tool. Select Deleted contents on the bottom of the application and then wait. After the Items have been listed select the items you want to restore, right click on them and select recover items. Then wait. If a dialog box pops Open that wants you to confirm that you really want to restore the items click OK. Maybe the program runs into an unexpected error, this might happen if you try to restore several thousend objects at the same time. Click Continue there and go check for your Items. Usually the Items are restored before this message appears.

For the usage of PFDAVAdmin I would advise you to user a server that is neither Exchange Server nor a Server 2008 based operating system. You can try to run the tool on Server 2008 but in my case I ran into an error when connectiong to the exchange server. If you start the application on a Server 2003 based machine you will be able to connect to the exchange public folders.

]]> http://blog.the-exe.org/restore-deleted-content-in-public-folders-on-exchange-2007/feed/ 0