@StrongBad Yes now the issue is resolved

@thecreativeone91 said:

@Dashrender said:

@thecreativeone91 said:

@Dashrender said:

Not in many users, back when Core was first introduced... It's possible/likely that many vendors selling products meant to be installed on Windows Server now work with Core.

What applications are you referring? Most things that run on a server could care less if they are a gui or not as they primarily run as services. MS Dymanics is not supported on Core and I've never done it on core nor would I try it.

Symantec Backup Exec wouldn't run on Core back in the 2008 R2 days. Yes a client would work to Core, but the main install couldn't go on a Core server.

Backup Exec, you mean the product that's always had lots of problems since symantec took it over. and they took years to even get server 2012 support. Backup Exec is a black sheep anymore.

Yep I'm talking 5-6 years ago ....

@Dashrender said:

@scottalanmiller said:

@thecreativeone91 said:

This keeps sounding more and more like an attack to me.. Maybe they will release details. but if that's the case I doubt they will as to not have more negative PR about it.

This is what I thought but we know these guys well and they responded quickly to us. It was a hardware maintenance window (hence the time) and they had hardware fail during an upgrade.

That caused most of Canada to loose access?
damn..

Two separate instances I think.

Can't wait for the day they create a gateway device!!

Looks like I missed a lot of excitement today.

Looks like all is well.

ConEmu is a great tool. It can take PuTTY to a new level, making it feel a lot better integrated with the desktop.

Oh, okay. Well that's good 🙂

I agree, you probably need Lenovo to help you here.

The Jira products are very good. How do you want to use it?

@Lakshmana said:

@thecreativeone91 said:

listed on the server tag somewhere.

There is no password is present in the tag Sir

It should be in two locations like these:

HP_Proliant_ML360_G6_iLO_Stickers_01.png

post64ilo1.jpg

@scottalanmiller said:

Yes, but practicing lock picking doesn't require the caveat of "don't break into other peoples' houses." We assume that people know not to do that. If they don't, they shouldn't have lock picks.

I suppose I didn't assume 😛

@Dashrender said:

On a side note, anyone using C@C? I can't paste into the console window. Should I setup SSH first before trying to install this so I can use something like PUTTY?

Console window is a VNC session, it's graphical. You can't paste into those. No different than any KVM solution or OOB Management. Use an SSH session once your system is up and running.

The mango is missing for me in upper left hand corner.

I'll reboot and report back.

Stolen from that link: Go to control panel/services. Choose the mssqlserver service (or SQLExecutive/SQLAgent if they are failing) and then choose startup. Check what NT account is being used. Make sure that the password is correct and check with NT user manager that the account has not been deleted or expired.

If the account details seem ok, then check that it has "logon as a service" user right (again with user manager).

*If this doesn't resolve the issue then try logging on locally to the NT box with the same NT account and see what error(s) you get. *

@thanksaj said:

@IRJ said:

@thanksaj said:

@scottalanmiller said:

@thanksaj said:

Not true. What you saw there was 5.5. I was told by @Texkonc that VMware is looking to move away from the web client in the future. You can still use the installed client with 5.5. It works no problem.

In 5.5 the web client is definitely the official one.

I know it's the official one but the actual client installed works as well. They both work, even if the web client is the "official" one.

I seem to remember some features not working on the client.

I haven't had any issues with functionality up til now. I'm on 5.5 and use the installed client exclusively.

It's considered depreciated, and they have announced it won't be updated going forward. The web client is missing a few features that the fat client has is the only reason its still available (specifically they say emergencies only). I'm also guessing this means the free version will be going away with 6 as the web vsphere client is part of the paid licenses. They've actually pulled the 5.5 Vi client from the website unless you have the direct links (http://vsphereclient.vmware.com/vsphereclient/1/9/9/3/0/7/2/VMware-viclient-all-5.5.0-1993072.exe)

@thecreativeone91 said:

@Dashrender said:

I know there used to be (and appears to still be) a problem using OEM keys on VL media. I only maintain an inventory of VL media, and the machine I was fixing needed the OEM media.

When Have you had a problem with that? I keep one copy of Windows 7 Pro 64bit and use it both for VLK, Retail and OEM keys. Never had an issue with it. But with oem key's you need to use the key on the COA not the key windows would show it's installed with, as this generates during activation and will have -OEM in the random key. System builder kits as the same as oem as well.

The windows 7 Enterprise I have is the only one that has to be VLK

You probably just need to edit the ei.cfg file on your iso then.

I haven't tried it in so long I couldn't tell you the last time I had the problem at all. In the end I dug through my archives and found the original install media and just used that.

@scottalanmiller said:

It maxes out the CPU on the Unitrends device or on the machine being backed up? We give Unitrends all the CPU it wants on the backup machine, so it can do all of the work that it needs to do.

On the client being backed up. Common issue I've run into several times. The link provides an awesome walkthrough about disabling it.

@JaredBusch that should be an easy thing for them to modify.

@GregoryHall
I have Office 2010 and it didn't 'connect' on mine either. the user will have either 2010 or 2007.

I did remember something about open,. so I was able to File, Open, and go that route... Just seems odd that it was there, and then it dropped.