"what they do" for the other it is "what they have to do and hope you do as little as possible." Keeping lots of cooks in their own
Let's use GoDaddy as an example, short of them not supporting a record type, what's the issue with GoDaddy DNS and registrar in one account - specifically?
That's a good one to look at specifically.
GoDaddy DNS is cumbersome to use and wastes time. This is a vendor issue, not a bundling one.
GoDaddy DNS has a less than stellar uptime track record. This isn't a service they are known for, they don't really care as serious customers don't use it for this.
Under normal operations, non-IT staff should never have access to DNS records and IT staff should never have access to corporate identity records. Using GoDaddy for both removes the possibility of keeping those highly critical roles separate and puts the company in danger of IT running off with the company identity and business people of accidentally taking services offline.
As above, there is no safe means of using contractor support for simple IT tasks.
GoDaddy doesn't offer key DNS related features like caching.
You are either stuck using a single registrar (often not even possible as different registrars offer different domains) or stuck managing DNS is multiple locations. It lowers flexibility.
An outage from your registrar can take out your DNS with your risk mitigation removed as part of the outage. Otherwise a DNS outage can be protected against from the registrar and a registrar outage has no production impact. This is the biggest issue, it creates a whole form of risk that need not exist.
The lead in music was significantly louder than the audio after the lead in. that is bad.
That's been since addressed. Actually both things have. The videos from today (not posted yet) are with a still camera and audio tweaking. My dad does the final edits, and he added the intro music. So hopefully those two things are taken care of in about two videos from now.
I found this very interesting, since I'm switching to IT from education I always saw certifications as state mandated in order to even be considered for a position.
Oh yes, in many cases if you want a government IT job you will require certs. In fact, you'll be required to have certs from other industries. That's the degree to which government IT isn't considered professional. Government IT often pays a fraction of the industry and is not taken seriously. In NY state, for example, top level IT technical positions are often below entry level in pay. So below the professional scale.
So if your goal is "government IT" which is sort of its own thing, you'll need certs from non-IT to even be allowed to be hired. But it's often considered on the fringe or outside of "real" IT.
Keep in mind that while we often use IT Professional, as a term, IT are not professionals. Actual "professional" guidelines are actually considered insulting in IT. The idea that IT could be certified or that university education would be meaningful, the very tenants of professional work, are insulting in IT where things are performance based, not government pseudo-union based. A better term to use, at least in your head, is IT Practitioner, not professional. IT does not function if held to the standards of normal "professions". The education or certification needed for those fields are far too low to be useful in IT. The breadth of knowledge and continuous education needed for IT success are much higher than many other fields. This is why it is not considered polite or appropriate to compare IT Practitioners to something like doctors. The bar for being a successful doctor is embarrassingly low for IT, for example.
@sully93 I have a video from MangoCon 2016 where instead of talking about "what isn't IT" I talk about what it is. I have a recent SAMIT video on separating IT from SE. I'll do one soon on separating IT from Bench.
Listened to this on Friday. Thank you for reinforcing what I have been saying for about a year now around my company.
People in production brings in equipment that requires network connection and ports open to a cloud server, but does not inform us of these needs until after the equipment has been installed and wonders why its not working.
"Well no wonder why it is not working. We have to run a network connection into a production environment, give your equipment (that I just met, potential security issue) an IP address, and open ports to a cloud system that I have no idea about and no control over. All because you did not value IT enough to include us in the decision making processes to figure out if it would be compatible with our environment."
The basic information on how the certs work from 1996 still apply today. That's 21 years and counting. It's not expected to change for the next several years at least. The MTAs were a pre-pro cert added later, but as they are pre-pro and are not on the roadmap, that's not really a change. They've very slightly altered the MCP name, but that's fine as it was so ridiculous and pointless anyway. It's a bit like the SATs, after the mid-2000s they had to "dumb it all down" a little bit as it was just too hard for their audience.
But the MCSA and MCSE have remained pretty staunchly in place except for a really brief rebranding period that they immediately reverted, for decades and while they are much easier than they used to be, they remain in the same market position as always.
This is what MangoCon is for, you should all attend.
9 days until the big event!
I haven't been told no, but we are short staffed and I seriously doubt I'm going to be able to go. I am going to be there for the stream though.
The shorter the staffing, the more that they need to keep you happy. Remember, desperate bosses are pliable bosses.
Well I am taking off after 12 today and off tomorrow to be there for Laura in her time of grieving. I technically only have 1 more day off for the year :\
Technically you have all that you want, he can't afford to get rid of you. And you don't want to stay, so you have ALL of the leverage. Literally, all of it. He has everything to lose and you've got nothing on the line. You hold all of the cards. And it is not days off, he can still email you and ask you things, you are doing company training that helps him, etc.
Except that I'm sure he doesn't want to be without a paycheck while looking for his replacement job.
But chances are, he "doesn't want that" less than his boss wants to "lose his company because he can't fulfill his contractual obligations."
Oh and they provide the hyper v integration as cab file (guest agent):
I cant belive I complained when VIRT IO Tools was repackaged some time ago and they changed some folders in there ISO image, while MS gives you a .cab file and not even an executable.
What do you mean? What VM are you trying to install? You shouldn't need any integration tools at all for any modern operating system on a VM. They come built in and are updated via Windows Update (if running Windows OS)
If you install RHEL or CentOS, you can download a Linux Integration Services .ISO if you need to. You simply run the ./install.sh file. All other modern Linux OSs already have the Hyper-V Integration built in to the kernel.
The following files are available for download from the Microsoft Download Center.
Operating system Update
All supported x86-based versions of Windows 8.1 Download Download the package now.
All supported x64-based versions of Windows 8.1 Download Download the package now.
All supported x64-based versions of Windows Server 2012 R2 Download Download the package now.
All supported x64-based versions of Windows Server 2012 Download Download the package now.
All supported x86-based versions of Windows 7 Download Download the package now.
All supported x64-based versions of Windows 7 Download Download the package now.
All supported x64-based versions of Windows Server 2008 R2 Download Download the package now.
Go to the download, and it is all .cab files.
WTF are you talking about. This is not DVD media. You are doing it wrong from the beginning.
Ofcourse I know this is not DVD media, those are the Hyper-V agents that MS wants you to install on your guest machine, MS calls them Hyper-V integration components.
ESXi and KVM Virt IO all provides much better ways to get this installed on your guest machines, and dont provide you a dumb .cab file.
Just because you are not capable of providing a share to get access the files from within the VM does not mean the process is stupid.
Who wants to mount ISO files from the hypervisor all the time just to update software in a guest VM? That is the stupid thing.
Okay, granted what are the commands to create share in Windows hyper-V standalone? I tried and failed, or the only way to do so is to have share outside hyper-V like NAS ? if so both KVM and ESXi can be easier in sending files directly to the host.
I dont want to go to fight about who is the best Virtualization platform cause that is pointless, but my trial wit Hyper-V is everything required 2 extra steps to get it configured. While the competition it can be done with one step.
Why are you trying to put these files on the hypervisor? They have no need to be on the hypervisor. You cannot download them there anyway why are you trying to put them there? The guest VM does not care where they are shared from. Just put them someplace accessible. or even download them directly in the guest VM.
I am not arguing best hypervisor platform. I am simply stating you are doing things wrong and causing your own problems.
I'm guessing that he might be saying that he has no NAS, and doesn't want to create a share from his desktop machine to make those ISOs available to the hypervisor.
ESXi allows you to have a folder on the DataStore that you can then reference. I did this for my ESXi server. Same goes for my XS, I had a local piece of storage on the hypervisor for ISOs.
I don't see an actual issue with this. The biggest one I seem is that you might be using more expensive disk to store ISOs instead of storing them on a NAS.
And Hyper-V lets you access share a folder too. It is all windows, so the admin share is there and active.
Guy didn't know how to set the timezone on a Windows system, and jumped the conclusion that Microsoft just royally screwed up / couldn't figure out time zones, and gave up.
We had a client's onsite IT guy put in a ticket that the exchange server was 2 hours off! Nope, what recently changed?
You rebuilt your laptop and just changed the time and not the default pacific timezone.
Point us, -100 for you being the IT guy.