www.geekadmin.com

Tough day?
Cloning and setting up a lot of machines?
And you receive this error:
“Your computer could not be joined to the domain. You have exceeded the maximum number of computer accounts you are allowed to create in this domain. Contact your system administrator to have this limit reset or increased.”

And now? what you have done?

Active directory has a “quota” for how many machines a user can join in domain by day, to change that you are going to need to install the support tools or go the domain controller.

Follow this steps:

1. Run Adsiedit.msc as an administrator of the domain.
2. Expand the Domain NC node. This node contains an object that begins with “DC=” and reflects the correct domain name. Right-click this object, and then click Properties.
3. In the Select which properties to view box, click Both.
4. In the Select a property to view box, click ms-DS-MachineAccountQuota.
5. In the Edit Attribute box, type a number. This number represents the number of workstations that you want users to be able to maintain concurrently.

Look in this picture to have a clear idea:

Click Set, and then click OK. Like it? Please leave a commen, be nice

When you try to execute an application the following error appears:

“Application Error : The application failed to initialize properly (0xc0000135). Click on OK to terminate the application.”

This is an easy fix.

The application developer used the .Net Framework, juts install the framework and Re-run the application

Remember to Reboot

Easy? Feeling grateful? Just leave a comment saying thanks

You got the error “Process INETINFO.EXE (PID=1748). Topology Discovery failed, error 0×8007077f. ”
On your event viewer after you changed the IP from your server, and you don´t know what is it.
This error can appear on DSQuery, OWA, OMA and others Exchange 2003 and 2007 Servers.
What this error means?
It means the Exchange Server doesn´t know wich site it is located.
There is a great possibility you don´t include the new subnet on the list of your sites..
So Let´s fix It.

1. Open Active Directory Sites and Services
2. Go to Subnets

Check if your new IP has an subnet there. If not Include it.

3. Include the new subnet (remember class c = 255.255.255.0)

4. Wait 15 minutes or replicate the server manually.

I restart the server just to make sure he gets the new info.

After that your problems should go away
Any more questions enter in the forum.

You open your disk Management Tool and see your Dynamic disk as Healthy but it says (At Risk) on them.
So what is really happening.

In general this kind of problem happens when you have any I/O error, maybe a latency in the SAN, maybe one disk write or read fails. So be aware and check if everything is ok.

Clicking in Re-activate will clean this error, but if it keeps appearing take care, something very bad is happening and can corrupt your data.

Your fellow users, start to get their vacations and complain about this error on Outlook 2003 or 2007.

So what you do now?

This is a tricky problem, frequently this is an error on your local Outlook profile, If you go to the OWA everything will work without problem.

You may try running Outlook with the /cleanrules swith or just delete the .ost files and start a new perfil.

Remember .OST files. This files are created for the outlook cache function.

If you havy any comments or questions please visit our forum

http://www.geekadmin.com/forums