Convert OST to PST

Posted by Simson on January 19th, 2010

There are many third software would help you for this you may try their demo it works fine, but the full version would cost you around $200 which is costly

But i was having alot of trouble then i buy one of them.

I would help you doing this but i can only recieved files since i may not install the software at your PC and ask me to remote desktop to and install on your PC because the licences,

Please fell free to contact me if you need help. I proven to restore OST 10GB size.

regards,

Sim

Tips on changing message size limit on Exchange 2007

Posted by Simson on August 27th, 2009

#Get Organizational Limits
Get-TransportConfig

#Set Orhanizational Limits
Set-TransportConfig -MaxSendSize 20MB -MaxReceiveSize 20MB -MaxRecipientEnvelopeLimit 300

#List Send Connectors
get-sendconnector

#List Send Connectors with details (using Format-List/FL)
Get-SendConnector | FL

#Set Send Connector Message Size Limit for a specific connector
Set-SendConnector -Identity “Default Internet Connector” -MaxMessageSize 20MB

#Set Send Connector Message Size Limit for all connectors
Get-SendConnector | Set-SendConnector -MaxMessageSize 20MB

#List Receive Connectors
Get-ReceiveConnector

#List MaxMessageSize for all Receive Connectors
Get-ReceiveConnector | FL MaxMessageSize

#Set MaxMessageSize for a specific receive connector
Set-ReceiveConnector -Identity “EX-2K7\Default EX-2K7″ -MaxMessageSize 20MB

#Set MaxMessageSize for All Receive Connectors
Get-ReceiveConnector | Set-ReceiveConnector -MaxMessageSize 20MB

#Get MaxSendSize and MaxReceiveSize Mailbox Limits for a user
Get-Mailbox BAndersen | FL MaxSendSize,MaxReceiveSize

#Set MaxSendSize and MaxReceiveSize Mailbox Limits for a user
Set-Mailbox -Identity BAndersen -MaxSendSize 40MB -MaxReceiveSize 40MB

Howto : Windows root\system32\hal.dll missing

Posted by Simson on August 24th, 2009

1)Press F2 for Setup utility
2)Use down arrow key and select Boot Sequence<>
3)From the 4 choices given I arrow down and stop at IDE CD-ROM Device
and press left arrow key to move to first choice. The rest of the
choices I uncheck by pressing the space bar.<>
4)Place Operating disk in CD-Rom. My OS is Windows XP Home Edition.
5)Hit the Esc key and enter to save changes and exit.
6)Press any key to boot from Operating System (OS)CD.
7)Let windows setup load files from CD
8)Select R, at recovery console.
9)You should now see: 1:C:\Windows
10)You’ll be asked, “Which installation would you like to log onto”
Select 1 <>
11)Then you’ll see: “Type administrator password:” I have none so I
just again.
12)You’ll return to C:\Windows> TYPE bootcfg (hit spacebar)/rebuild
(should look like this, bootcfg /rebuild)
13)You will now see this message: “Scanning all disks for windows
installations Please wait since this may take a while.” Took me
less than 10 minutes to scan.
14)You will now see, “Add installation to boot list? (yes/No/All)
Select yes.
15)Enter load identifier: (this is your OS on your computer.)Here I
type: Microsoft Windows XP Home Edition.<>
16)Now you’ll see: “Enter O.S. Load Options:” TYPE /fastdetect (one
word)
17)You will return to the C:\Windows (remove your OS CD from your CD
tray) TYPE exit and
18)Hit F2 for setup (again!)
19)Scroll down to boot sequence and
20)Hit left arrow key to move up and select, Hard-Disk Drive C: press spacebar to re-check choice. I now unchecked the CD-Rom choice.
21)Hit the ESC key to save changes and exit.

At this point my windows XP loads as if nothing happened. It sadly disappears when I use it again and have to repeat these steps!!!
I’m currently looking to see what solution I find that will help me load it normally with out having to repeat these steps. Thankfully I can use my husbands computer to at least get this far. Hope this works for you all as well.

Source : http://www.nocrash.com/ncbbs/msgs/162.shtml

Remote Desktop Client Disapear Solution

Posted by Simson on August 21st, 2009

I don’t know why, but I have lost my remote desktop connection in programs. How can I return this to my programs?

From what you’ve described, you have lost your shortcut somehow. This can be recreated using the method listed below:

Using Windows Explorer, navigate to:

C:\Documents and Settings\All Users\Start Menu\Programs\Accessories\Communications

Right click in the right hand pane and select New>> Shortcut.
This should launch the Create Shortcut Wizard.
In the Location text box, enter: mstsc.exe
Click Next.
Name the shortcut; Remote Desktop Connection
Click Finish.
Test the function of your new shortcut.

Easily kill remote desktop sessions to your server

Posted by Simson on July 27th, 2009

This is more of a future reference post, but if you have the same problem we sometimes face with lots of developers logging into the same remote win2003 server, where both terminal sessions are taken. And sometimes both are taken by the developer who’s just gone on holidays! So then you either have to drag you butt down to the server room to kill sessions from the terminal or even worse ring up the data centre for a hosted box.

Well fret no more! you can run the following commands easily to kill any remote sessions to a box from a winXP (and vista i presume?) or parallels for the macl33t

1: Open windows command prompt

2: to view current connections: qwinsta /server:myserver

This results in an output of

SESSIONNAME USERNAME ID STATE TYPE DEVICE
console administrator 0 Active wdcon
rdp-tcp 65536 Listen rdpwd
rdp-tcp#51 administrator 2 Active rdpwd

3: kill a session by: rwinsta [sessionID] /server:myserver

i.e. rwinsta 2 /server:myserver

Microsoft Launched Microsoft Exchange 2010

Posted by Simson on April 16th, 2009

Overview
Microsoft Exchange Server 2010 Beta helps IT Professionals achieve new levels of reliability with greater flexibility, enhanced user experiences, and increased protection for business communications.

* Flexible and reliable – Exchange Server 2010 gives you the flexibility to tailor your deployment based on your company’s unique needs and a simplified way to keep e-mail continuously available for your users.

* Anywhere access – Exchange Server 2010 helps your users get more done by giving them the freedom to securely access all their communications – e-mail, voice mail, instant messaging, and more – from virtually any platform, Web browser, or device.

* Protection and compliance – Exchange Server 2010 delivers integrated information loss prevention, and compliance tools aimed at helping you simplify the process of protecting your company’s communications and meeting regulatory requirements.

This software is intended for evaluation purposes only. You must accept the license terms before you are authorized to use this software. There is no product support for this trial software. You are welcome to participate in the forums to share your trial experiences with others and to ask for advice.

Top of page
System Requirements

* Supported Operating Systems: Windows Server 2008; Windows Vista 64-bit Editions Service Pack 1

* Operating System for Installing Management Tools: The 64-bit editions of Windows Vista® SP1 or later, or Windows Server® 2008.

* PC – x64 architecture-based computer with Intel processor that supports Intel 64 architecture (formerly known as Intel EM64T) or AMD processor that supports the AMD64 platform

Additional requirements to run Exchange Server 2010 Beta

* Memory – Minimum of 4 gigabytes (GB) of RAM per server plus 5 megabytes (MB) of RAM recommended for each mailbox

* Disk space

o At least 1.2 GB on the drive used for installation

o An additional 500 MB of available disk space for each Unified Messaging (UM) language pack that you plan to install

o 200 MB of available disk space on the system drive

* Drive – DVD-ROM drive, local or network accessible

* File format – Disk partitions formatted as NTFS file systems

* Monitor – Screen resolution 800 x 600 pixels or higher

Exchange Server 2010 Beta Prerequisites
If these required prerequisites are not already installed, the Exchange Server 2010 Beta setup process will prompt and provide links to the installation locations; Internet access will be required if the prerequisites are not already installed or available on a local network.

* Microsoft .NET Framework 3.5

* Windows PowerShell v2

* Windows Remote Management

Actual requirements will vary based on system configuration and specific features installed. For more detailed system requirements, please refer to the Exchange Server 2010 Technical Documentation Library.

For a list of Windows Server 2008 requirements,
visit http://technet.microsoft.com/windowsserver/2008.
To Download this Beta version visit: Download Microsoft Exchange 2010


Copyright © 2007 Free Cookies for Linux & Windows. All rights reserved.