Accidentally I deleted the folder called office information in outlook, and it is an important folder to give user information about office in my organization.
After searching from google I found a tools to restore folder from public folder in exchange 2003.
The tools called PFDAVAdmin.exe, you can download it from here
And for the steps you can do the following step (based on Microsoft kb 924044)
For the step 1 : download the tools
Step 2: Recover a deleted public folder
Move to the PFDAVAdmin folder, and then double-click the PFDAVAdmin.exe file.
On the File menu, click Connect.
- In the Exchange server box, type the name of the Exchange server to which you want to connect.
In the Global Catalog box, type the name of the global catalog server. To find out the global catalog do the nslookup like this
- If it is required, click to clear the Authenticate as currently logged-on user check box. Type an appropriate user name, password, and domain in the respective boxes.
- In the Connection area, click Public Folders, and then click OK.
- Expand Public Folders, and then click the parent folder of the deleted folder.
- Right-click the parent folder, and then click Show deleted subfolders. The deleted subfolder is shown in red.
- Right-click the subfolder, and then click Recover folder.
- Click OK to acknowledge the Recovery succeeded message. The recovered folder name appears as Folder_NameRecovered.
- Test access to the folder by using an e-mail client.
- In Exchange System Manager, right-click the recovered folder, and then rename the folder.
Step 3: Recover a deleted item
In PFDAVAdmin, open the folder that contains the deleted item.
- Click the Items tab, and then click Deleted items.
- Right-click the item that you want to recover, and then click Recover items.
- Click OK to acknowledge the Recovering these items message.
Hope it help J
To solved the problem, please do below workaround :
- Go to start – all programs – accessories – right click on command prompt select “run as administrator”
And Then type below command :
net localgroup administrators localservice /add
net localgroup administrators networkservice /add
- And then restart your computer.
Hope this help some people. J
Credit to Steven Wright, because this article help me so much. If you have problem like me, please follow below procedure to resolve it :
Connect putty and logon into xen server host using root user.
Use “vi” (a text editor) to edit the /etc/logrotate.conf file
Changed the rotate value into what you want and set the log to compress (delete the #).
Press “I” for insert and press “x” to delete. Esc to return to command mode.
After finish, press “:wq” (w = Write and q= quit).
If the client have duplicate SID, it’s make computers not showing in the wsus console.
The duplicate SID are came from Image base deployment .
If you generalize the image using sysprep this issue will not show.
You can run this bat in the client that not detected in WSUS console.
Credit to original script creator.
In my Last IT audit, I had to get MBSA data from all workstation and server.
And when doing it, I have problem like below picture :
To solved this, you just need to start remote registry services, and then do the scan again.
Set the remote registry to automatic if you want to remote registry run automatically.
Today I have a problem when I want to create new image using the existing image(old image) in citrix xen server.
When I run sysprep, I found an error message “A Fatal error occurred trying to sysprep the machine”
To solved this problem, I do a this workaround :
- Change registry key HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus to 7
- Change HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\SkipRearm to 1
- And then Delete the folder Panther.
- And then run sysprep again.
http://social.technet.microsoft.com/Forums/windows/en-US/425bd101-8a87-488c-b2e2-9f2f8113a0d9/sysprep-fatal-error-occurred-while-trying-to-sysprep-the-machine (look at for Riffing answer)
WSUS Server may report that some clients (Windows Server 2008R2) need the update “Windows Server Manager – Windows Server Update Services (WSUS Dynamic Installer (KB972493).” The clients not detect that, they need this update but the WSUS server label the client as needing the update regardless.
And this is the option for solved that :
1) Decline the update in WSUS for all groups. But you must make sure this update already installed on your WSUS Servers. This will make all server clean without notification that show the server needed that update.
2) Setup a separate group in WSUS for just your WSUS servers. Approve the update for the WSUS Servers group and not the other servers.
If seeing “Install (1/5)” in WSUS irritates you and makes using WSUS more difficult like it does me, pick option #1 like I have. You’ll know when WSUS SP3 comes out because WSUS will present it as a new update for you to Approve, Decline, etc. When you see this, go update your WSUS servers.
(Option 3 is to install the WSUS role on all your 2008 servers – not sensible and not recommended.)