Altiris is not going to work on Windows XP 64bit, Windows Vista 64bit and Windows Server 2003 64bit. I tried myself on Server and Vista and both installations ended with warning show below.
Too bad ;-(. I read an artical on juice site of Altiris that verios SVS 3 will support the 64 bit operating systems.
Couple hours ago I created the tutorial how to get VMWare ESX server within VMWare Workstation 6.
Still working to post the screencast and need to find out the right procedure to export the media file.
Today I will visit the Dutch VMWare User group day in Nieuwegein, The Netherlands. For me this is the first and I am really excited and I hope I will see a lot of new things in the hardware virtualization arena.
The following sessions are planned in my schedule:
9:30-9:45 Start VMUG Event 2007: ‘Exploring the boxes’
9:45-10:30 Centrale sessie verzorgd door Equallogic
10:45-11:30 ESX Server 3.5
11:35-12:20 VMware Lab Manager
12:20-13:15 Lunch
13:15-14:00 Business Continuity for Virtual Infrastructure
14:00-14:15 Break
14:15-15:00 Virtual Desktop Infrastructure
15:00-15:05 Break
15:05-15:50 Advanced Storage Basics
15:50-16:05 Korte Pauze
16:05-16:50 VMworld 2007 in a nutshell
For more info on the event go to http://www.vmug.nl/.
Yesterday I created two tutorials for VMWare Workstation 6 Team.
Due to migration and tests between VMWare Workstation and Virtual Server 2005 R2SP1 I created two domain controllers for Networknet.nl domain. At some point I had issues with the DNS and than I assigned the IP address of my second DC of the domain to the primary one.
Right now all my domain clients are reporting the error message below. The kerberos client received a KRB_AP_ERR_MODIFIED for the domain controller account. I have seen this before and will fix it by deleting the complete DNS records for Active Directory.
Screen clipping taken: 12/2/2007, 2:18 PM
Open Computer Management console and scroll down to DNS snap-in. Locate your _msdcs zone and select all record except for the (same as parent folder). Right click and delete them.
Screen clipping taken: 12/2/2007, 2:21 PM
Go to your primary AD zone and select all other AD related records.
Screen clipping taken: 12/2/2007, 2:24 PM
As shown above; select and right click for deletion. Check the hostnames for the domain controllers with correct ip address.
Now the DNS zones are clean. To fix the recreation of all required records for Active Directory you can do the following.
Verify the records after the reboot if restart of the service.
These steps are executed in a lab environment and be careful when deleting the DNS AD related records in a production environment. If there are dozen of domain controllers; restart or reboot is also required on all of them to get the records back.
What happens in the background is that file C:\WINDOWS\system32\config\netlogon.dns is being imported into the DNS zones.
My inbound email flow on the Exchange 2007 server didn’t work. I was able to send out my emails using the exchange server, but when receiving them the messages were bounced. During my last weeks migrations I configured second mx record at my hosting provider and all emails were caught there; because I also configured outlook to pull that mailbox it seemed that everything worked fine. After getting a strange message at LinkedIn and Gmail I started to troubleshoot and read the error messages.
At Gmail.com I’ve got the message below:
After reading this message I immediately went back to my Exchange 2007 Receive Connector and verified the authentication and saw that TLS was selected.
I unchecked the TLS settings and applied the Receive Connector configuration. Resend the email from Gmail to my primary account and the email failed again.
I went back again and this time to Network tab of the Receive Connector. I run the ipconfig and saw that the ip addresses did not match. Changed the binding ip address to one assigned to the server and my test from Gmail succeed this time. I can’t figure out why this setting was wrong; maybe I overlooked during the installation and configuration of the Hub Transport role and did not open the properties of my receiving domain.
I am happy my inbound email traffic is flowing into the Exchange store and filling up with SPAM.
Recent Comments