Careers

We empower you so you can give us your best. It's that simple. We assume you have personal mastery, so you won't find an excess of rules about how work gets done. The pace is fast, we trust people to do the right thing, on their own, most of the time. Coaching, mentoring and low-key leadership are there when they're needed. Everyone in our highly diverse workforce has the chance to grow toward their own personal definition of success. We cultivate a work environment that liberates, not blocks, the best in you by offering:

Stimulating career challenges and advancement opportunities.
The chance for grass-roots innovation, with bottom-line impact.
A variety of basic-to-advanced training programs.
Flexible work schedules that factor in your personal commitments to home life and cultural make-up.

You need the right tools to do your work. Whether you're a technologist or not, expect state-of-the-art technology at D&K Enterprise, LLC to help you do your job right. We strive to integrate the best that technology offers into our work flow. And we're committed to staying on the leading edge, focused on building our e-commerce channels in parallel with technology-driven processes.

If you are interested in joining our team, please fax your resume to (954)622-8425

 

 

Microsoft Virtual Server

I just love this tool. We've implemented it in a plethora of ways.
Yesterday one of our clients needed to setup a terminal server for using Tax
Wise and had Microsoft Windows Server 2003 R2 for Small Business Server.
We'll, they were way under utilizing the server that they had so we
installed Microsoft Virtual Server 2005 Standard(freely offered through
Microsoft), and installed Server 2003 Standard on the virtual machine.
Perfecto. After setting up the proper routes, securing the RDP connection
with High encryption, and testing they were ready to go. We emailed them a
link to remote in using Terminal Services, or Remote Desktop Connection for
Mac and they were happy as can be!

Printing Locally from a Remote Server

A few of our users were having difficultly printing to their local printers from the terminal server that they remote into. The terminal server had the EOL print driver installed on it and I could see that most of the users who connected could print to their local printers and that the printers were using the EOL driver, I could see this by checking their printer properties/print drivers. What we then did was to insure that the EOL driver was installed on the client computers and that the users had modify rights to the 3 eol files located under the system32 folder, after these rights were granted the printers began showing up on their remote sessions and they could print locally.  

Should you use NTFS compression on Exchange Server files?

Serdar Yegulalp
01.10.2007

The sheer size of many Exchange Server files -- the database, mainly, but
also the log files -- can eat up a lot of disk space. Any hard drive that's
over 75% to 80% capacity is going to be hard to defragment (especially if
it's already badly fragmented), and will experience other performance
degradations on top of that.
To alleviate the problem, some Exchange Server administrators have debated
using NTFS's native file-compression system on some Exchange Server files to
save hard drive space -- but this is generally not a good idea..
When people think of NTFS file compression (which allows files to be
compressed and decompressed on the fly), they think of technologies like
Stacker or Disk Doubler -- which were not terribly stable and caused at
least as many problems as they solved.
Back when disk space was at a premium, these NTFS compression solutions were
at least provisionally attractive. But now that disk space is so much
cheaper, it makes more sense to simply buy the storage you need instead of
wrestling with a software solution.
Granted, NTFS file compression is a lot more dependable now than the
technologies that were available back in the days of DOS and 16-bit/32-bit
Windows. Even so, I would still be reluctant to use it to compress live data
on any production machine, especially data used by Exchange Server.
The main reason for not using NTFS file compression on Exchange Server is
performance. There's a certain amount of overhead involved in compressing
and decompressing data. If you multiply that overhead by the number of
concurrent I/O requests made to such data, you have a recipe for an Exchange
server that's going to take a performance hit -- no matter how many cores
you have in it. The Exchange Server databases themselves (and the binaries)
should never be compressed.
The only Exchange Server files that I would feel comfortable setting as
NTFS-compressed would be Exchange Server log files -- not the transaction
logs -- but logs generated by SMTP logging.
SMTP log files do compress very well -- 75% or better, since they're
essentially plaintext. But if they're not really needed, they can simply be
archived using a third-party archiving tool that yields better compression
than NTFS on-disk compression; or you could just delete them entirely.

Don’t use Host.Net

Question

I upgraded my boss to a new machine. She is complaining that the autopopulate in her MS outlook addy bar doesnt list all her old email contacts. Is there any way to grab the cache or whatever that held her old auto populate address's from outlook 2003? and transfer that to her new comp using outlook 2007? I tried grabbing the *nk2 file off her old comp but her new comp didn’t have any *nk2 files or the folder in which I got it off her old comp.

Answer.

They are stored in the NK2 file. If it is not there then you are kinda out of luck. I hope your Christmas bonus does not depend on getting it back...

Here is some wisdom I learned a while back. Always image the boss' computer before upgrading it. Every CEO/CIO/etc. I ever met would pay the cost of Ghost/Acronis for their laptop.

Good luck.

Computer will not boot

Recently my company had a client that could not get his pc to boot up. Since I was doing remote support I was not physically in front of the pc in question. I had him try to get into safe mode however each key combination that we tried to get into the boot menu or the bios setup were unsuccessful, alls that the computer would do was to freeze on the Dell screen. Since we could not get into the boot menu or bios I thought that it might be a motherboard failure. I was also not able to remote into the pc from the server and could not ping it. The only option that I could come up with was to have him ship the computer to our office so that we could look at it and perhaps remove the hard drive to recover the data. It was only after setting up a new pc for him that I learned that he had an external hard drive attached to his pc, once he unplugged that the pc was able to boot, apparently it was trying to boot to the external drive which of course did not contain any OS