henazo

SCCM with discovery in WHD.

Yes you can! In fact I'm doing this in production tonight. Notice I said production right? That's because I tested this out in a stage environment with a backup of our prod db. There are major problems with the db if you're using SQL 05 or 08 that have to be corrected before the upgrade can complete. I opened a ticket with…

We started out with a SQL Express version because it was free. As we began to grow we started getting closer 10gb express db limit so we decided to go full fledged SQL. This was also great because we can now use the SQL agent for nightly backups. Sorry if this is not really the answer you're looking for.

Define "raise" please. Ticket creation via email or ticket creation via client login?

If you allow email ticket creation, leave subject for the request types that the initially created ticket will become. If you only allow ticket creation from client login and not email, go nuts! You can do what you want.

Yes! You'll have to use BB codes but it works really well. Example <font size="4">Text for FAQ</font>

This is the way it works: You have three tickets all same issue; #1, 2 and 3. You merge them into the newest ticket which is #3. 1 and 2 get closed and a note is added #3 for each of the other tickets. Now #3 contains references to #1 and #2 and remains open until a tech closes it.

I noticed the same error a few months back although my system is set up differently; daemons and site run on 2008r2 vm and sql db on 2012r2 vm. After updating to the 2nd hotfix for version 12.2 I haven't seen the error again.

No changes are necessary provided you already have the basics in place. * A forward lookup dns properly set in your environment and exposed * fqdn added in setup>general>options>server dns name (not a bad idea to force https here too) The email templates use tags to insert the ticket url into outgoing email, those tags…

If you use a SQL DB, then you could create SSRS reports based off that DB. 

I've been thinking about this and there might be a way to accomplish this. First of all, what you're asking for is not SSO. You may want to implement a SSO protocol but that depends on how you want clients to authenticate, be it against AD or using the WHD built in authentication method. Here are the two options that might…

Yes, take at look at mine. It's kind of basic as far as design, I've seen some really elaborate pages especially at universities: A client using the portal and sending an email will always be identified correctly provided you have accepted domains, client creation via ldap/email and a few other settings configured…