Been a lot of discussion on this, most good, some not. My 22 yr's worth of experience, from both sides of the fence and in both good and bad situations below.
First off and I realize that it's a bit late now, plan time into ANY admin's schedule for documenting procedure. Very few places that I have worked seem to realize the importance of planning this into the schedule, and almost none realize how randomized an admin's day becomes in such a short period of time. Give them time to breathe and expect others in the company to abide by it. These people are the ones that are keeping the wheels turning, give them a chance to keep their tools, documentation and house in order.
The documentation doesn't have to be written in detailed tech speak, but it should outline enough detail to allow a relative newcomer to be able to follow the notes and keep your company out of trouble. Any admin worth their salt will be willing to do this and be willing to share their knowledge. Being the priest/priestess of secret knowledge is old school and should get you shown the door. Sharing your knowledge shows that you're a team player and should entrust you with greater responsibilities and greater opportunities.
Second, do NOT alienate this person UNLESS there is a confirmed reason to suspect a potential security breach. If that case exists, get them out the door NOW and live with the consequences. Hire in whatever expertise you need to pick up the pieces, but don't put yourself at further risk by keeping that person around. If this person is has not given you reason to suspect malfeasance, then don't treat them like they're a criminal. Treat them with respect and professionalism.
Third, explain the needs that you have and ask their help and cooperation in minimizing the impact of their leaving. Do not be patronizing, be professional and clearly outline your needs (not expectations, your NEEDS, there is a big difference). Ask their buy-in to meet these needs. Ask them if they would be willing to extend their time with you in the case a catastrophe were to occur (so few places plan for this contingency). Jointly determine what set of conditions need to be met in order to bring your operation back online. If this person is willing to extend their stay under this contingency, come to an agreement on how long that extension would last. If not, you must to put a plan together to cover this contingency.
Fourth, ask them what they can do in the time remaining to help meet those needs and then clear their schedule of anything that would obstruct their ability to meet those agreed upon objectives. Explain that from your position, meeting those needs is now the most important set of objectives that they have to meet, everything else short of a major catastrophe is secondary, and MEAN it. From experience I can tell you there is nothing more frustrating than to have work that was deemed critical path interrupted by some user who was having trouble with a print job. (WTFO, I thought that I was to focus on this procedural documentation and not have to deal with this routine stuff. What is really important here, my knowledge or squeezing me for every last little fixit job?).
Fifth, explain that immediately AFTER they leave, the passwords and access that they have has to be changed, not by them. This isn't a statement of distrust, it's a matter of procedure and for security audit reasons. They should expect this and it should not come as a surprise, but it needs to be clearly stated and articulated for legal reasons. Outline what accounts are going to have passwords changed and what access methods are going to be disabled. Ask if there are other accounts/access methods that THEY know about that have not been mentioned. You're showing them the trust and respect they deserve and you're giving them the chance to show that that trust and respect is well placed. By offering the chance to present any remaining information that you may need to know and to confirm what needs to be addressed, you've covered your butt and theirs. This is CRITICAL.
Last, leave the door open. If this person was viewed as valuable enough to add to your team when they first came on, after they leave you may find that they had become even more valuable and you just didn't realize it. You may find that you want them back and for them the grass may not be greener after all.
If an admin is really good at their job, you won't even notice what it is that they do, that's what they should be striving to achieve. Too often, admin's are not very good at bringing their achievements to the attention of those that they work for, and as a result their work and achievements are overlooked and unappreciated. Guard against that and your retention of these contributors will be much better.