One of my clients cannot deliver email due to PTR Record not match with MX Records
Rejected by some of domain
Customer is hosting their own Public DNS, I try to update the PTR record, wait for more than 24 hour but still not propagation… finally I know why…
If your server is being managed by your hosting service provider, you may contact them for assistance. If you manage the servers yourself, then you may have to contact your ISP (e.g. Singtel, Starhub) to request for the configuration.
Normally, in Windows 2008 R2 will be easier to do sysprep, we just need to go C:\Windows\System32\sysprep\sysprep.exe then we can do the sysprep already… but when in previous version of Windows, will be using a different to run the sysprep.
What is Sysprep? Basically, when we want do a clone machine, if the security identifiers (SID) in 1 network, then it will crash. So we need to using the Sysprep tool to clone the machine and it will create different SID. Secondly, normally we do testing/ simulation in our lab environment, if we have the Sysprep image, it will easier for us to do testing.
How we sysprep Windows Server 2003? You can downlod the tools here
The file size is only 2289KB, WindowsServer2003-KB926028-v2-x86-ENU.exe
1. Install the hotfix WindowsServer2003-KB926028-v2-x86-ENU.exe
2. Open Deploy.cab at the location C:\WINDOWS\system32
3. Create new folder called sysprep at location C:\ and copy all file from Deploy.cab
4. Run setupmgr.exe from C:\Sysprep. The Setup Manager wizard starts. Click Next…
5. Select the correct OS version… Next…
6. Select “No, do not fully automate the installation”… Next…
7. Enter Name and Organization, Time Zone, Product Key, and Workgroup or Domain. The other settings can remain defaulted. Note that you don’t want to specify the computer name since you will be creating multiple computers from the base image and you don’t want to specify the admin password, even encrypted. If the sysprep program can extract the password from the answer file, so can any hacker worth their salt. Click Next… through to the end.
8. Finish… Save to C:\Sysprep\sysprep.inf. OK…
9. Wait while Setup Manager finishes. Cancel… (Yes, odd way to exit a program that has completed successfully.)
10. Run sysprep.exe.
11. Click OK.
12. Ensure that “Don’t regenerate security identifiers” is UNCHECKED. You want to regenerate the SIDs when each new clone boots.
13. Click Reseal, OK to confirm that you want to regenerate SIDs, and wait for the system to shut down.
It will auto shutdown, right now you will have 1 copy of sysprep Windows 2003 image!