Seeking how to improve
-
Well to start, you have begun the process which is an awesome sign, and you are here asking for help too. So we can help you and believe me you will learn here a lot out of your comfort zone.
You should be able to learn using LABs and even online testing. But if you would like to evolve your systems you should look at what you have been using for a while now, like what Network, Hardware and Software do you have deployed now? What should be changed, what can you improve? How can I grow my skills and it what areas?
So share with us that and we can help.
-
You and I have the same job.
-
lol me too.
-
Me three
-
@dashrender said in Seeking how to improve:
How about starting by sharing a list of your to dos, etc.
Well, that's one of my problems, trying to bite more than I can reallistically chew.
I have hundreds of items in my to do list, 90% "self imposed". As I keep learning, I keep adding ideas to improve the current infrastructure.
Then, I have a tought time trying to prioritize my work (too much items to process leads to something like analysis paralysis)
Also, trying to learn new technologies requires time, and that makes me question: should I improve my knowledge in the technologies in use at the moment or should I focus in learning more useful things for a near future?
Example: Should I improve my VMware skills (currently in production) or should I invest learning Hyper-V, PowerShell, PowerShell DSC, Puppet to be able to use that in a few months?
Our biggest project at this time is a total technology "refresh":
- Migrate from VMware vSphere Essentials to Hyper-V Server 2016
- Prepare to pass out the SAN (we have two ESXi diskless servers connected to an EMC array, going to Hyper-V with local storage)
- New network configuration (adding VLANs for a DMZ, a testlab, management interfaces... nothing fancy)
- New Active Directory domain/forest (we have a very old inherited domain that doesn't follow best practices)
- Upgrade from Windows Server 2008 R2 to Windows Server 2016
- Deploy standarized Windows (client and server) images using Microsoft Deployment Toolkit + WDS
- Manage software in client computers with Chocolatey
- Document everything (going with Dokuwiki)
- Try to automate everything as much as possible with Puppet (using The Foreman) and PowerShell/PowerShell DSC
So, I will be really busy for months...
-
@dbeato said in Seeking how to improve:
Well to start, you have begun the process which is an awesome sign, and you are here asking for help too. So we can help you and believe me you will learn here a lot out of your comfort zone.
You should be able to learn using LABs and even online testing. But if you would like to evolve your systems you should look at what you have been using for a while now, like what Network, Hardware and Software do you have deployed now? What should be changed, what can you improve? How can I grow my skills and it what areas?
So share with us that and we can help.
Thank you!
I will start a really big technology refresh in a few weeks. Please, take a look to my @Dashrender reply...
I think that time management and priorization are my biggest problems at this moment. Too much to do and learn. Not enougt time for everything.
The lab is a great idea. On my todo list for sure (Hyper-V on Windows 10 rocks for this)
But is really great having a community like this. Glad to have found you, guys!
-
I'd start by looking at that list you have and moving the '10% company goals' on to a 'urgent list'. Stick the other '90% self imposed' on to a 'long term goals' list. Remember, not everything now. Plan a year or two and schedule those projects. Planning is a great way to help the issue you have.
-
@manheraz said in Seeking how to improve:
@dashrender said in Seeking how to improve:
How about starting by sharing a list of your to dos, etc.
Well, that's one of my problems, trying to bite more than I can reallistically chew.
I have hundreds of items in my to do list, 90% "self imposed". As I keep learning, I keep adding ideas to improve the current infrastructure.
Then, I have a tought time trying to prioritize my work (too much items to process leads to something like analysis paralysis)
Also, trying to learn new technologies requires time, and that makes me question: should I improve my knowledge in the technologies in use at the moment or should I focus in learning more useful things for a near future?
Example: Should I improve my VMware skills (currently in production) or should I invest learning Hyper-V, PowerShell, PowerShell DSC, Puppet to be able to use that in a few months?
Our biggest project at this time is a total technology "refresh":
- Migrate from VMware vSphere Essentials to Hyper-V Server 2016
- Prepare to pass out the SAN (we have two ESXi diskless servers connected to an EMC array, going to Hyper-V with local storage)
- New network configuration (adding VLANs for a DMZ, a testlab, management interfaces... nothing fancy)
- New Active Directory domain/forest (we have a very old inherited domain that doesn't follow best practices)
- Upgrade from Windows Server 2008 R2 to Windows Server 2016
- Deploy standarized Windows (client and server) images using Microsoft Deployment Toolkit + WDS
- Manage software in client computers with Chocolatey
- Document everything (going with Dokuwiki)
- Try to automate everything as much as possible with Puppet (using The Foreman) and PowerShell/PowerShell DSC
So, I will be really busy for months...
Instead of analyzing all of the other things you have on your todo list, what you have here is a realistic starting point.
Take all of these things and start at the top and work your way down. I like the list in the order you have it
-
@manheraz said in Seeking how to improve:
@dashrender said in Seeking how to improve:
How about starting by sharing a list of your to dos, etc.
Well, that's one of my problems, trying to bite more than I can reallistically chew.
I have hundreds of items in my to do list, 90% "self imposed". As I keep learning, I keep adding ideas to improve the current infrastructure.
Then, I have a tought time trying to prioritize my work (too much items to process leads to something like analysis paralysis)
Also, trying to learn new technologies requires time, and that makes me question: should I improve my knowledge in the technologies in use at the moment or should I focus in learning more useful things for a near future?
Example: Should I improve my VMware skills (currently in production) or should I invest learning Hyper-V, PowerShell, PowerShell DSC, Puppet to be able to use that in a few months?
Our biggest project at this time is a total technology "refresh":
- Migrate from VMware vSphere Essentials to Hyper-V Server 2016
- Prepare to pass out the SAN (we have two ESXi diskless servers connected to an EMC array, going to Hyper-V with local storage)
- New network configuration (adding VLANs for a DMZ, a testlab, management interfaces... nothing fancy)
- New Active Directory domain/forest (we have a very old inherited domain that doesn't follow best practices)
- Upgrade from Windows Server 2008 R2 to Windows Server 2016
- Deploy standarized Windows (client and server) images using Microsoft Deployment Toolkit + WDS
- Manage software in client computers with Chocolatey
- Document everything (going with Dokuwiki)
- Try to automate everything as much as possible with Puppet (using The Foreman) and PowerShell/PowerShell DSC
So, I will be really busy for months...
As already mentioned by @dafyre, this is a pretty good list. I'd say because of this list, you've already dictated the path you need to take.
Should you bother with VMWare? Nope, you're company is moving away from it, it's useless knowledge at this point.
Your project list looks good. For each part of it, start a thread. It might be a good idea to start a thread first as a project over view - list the current environment, where you plan to go and why you choose that path. I'm sure this group will weigh in and perhaps help you tweak the path.
-
Are you worried about improving just your skills or are you trying to improve your career and make more money?
I dont think a company of 60 employees has a very high ceiling for IT salary....
-
@manheraz said in Seeking how to improve:
Our biggest project at this time is a total technology "refresh":
- Migrate from VMware vSphere Essentials to Hyper-V Server 2016
- Prepare to pass out the SAN (we have two ESXi diskless servers connected to an EMC array, going to Hyper-V with local storage)
- New network configuration (adding VLANs for a DMZ, a testlab, management interfaces... nothing fancy)
- New Active Directory domain/forest (we have a very old inherited domain that doesn't follow best practices)
- Upgrade from Windows Server 2008 R2 to Windows Server 2016
- Deploy standarized Windows (client and server) images using Microsoft Deployment Toolkit + WDS
- Manage software in client computers with Chocolatey
- Document everything (going with Dokuwiki)
- Try to automate everything as much as possible with Puppet (using The Foreman) and PowerShell/PowerShell DSC
That's a lot, but sounds like a good, solid list of stuff to be doing.
-
@jimmy9008 said in Seeking how to improve:
I'd start by looking at that list you have and moving the '10% company goals' on to a 'urgent list'. Stick the other '90% self imposed' on to a 'long term goals' list. Remember, not everything now. Plan a year or two and schedule those projects. Planning is a great way to help the issue you have.
Thank you for the advice, @Jimmy9008.
It's a bit difficult for me to priorize the list, but I'll try my best.
You are right: not everything now. That's the key.
-
@dafyre said in Seeking how to improve:
@manheraz said in Seeking how to improve:
@dashrender said in Seeking how to improve:
How about starting by sharing a list of your to dos, etc.
Well, that's one of my problems, trying to bite more than I can reallistically chew.
I have hundreds of items in my to do list, 90% "self imposed". As I keep learning, I keep adding ideas to improve the current infrastructure.
Then, I have a tought time trying to prioritize my work (too much items to process leads to something like analysis paralysis)
Also, trying to learn new technologies requires time, and that makes me question: should I improve my knowledge in the technologies in use at the moment or should I focus in learning more useful things for a near future?
Example: Should I improve my VMware skills (currently in production) or should I invest learning Hyper-V, PowerShell, PowerShell DSC, Puppet to be able to use that in a few months?
Our biggest project at this time is a total technology "refresh":
- Migrate from VMware vSphere Essentials to Hyper-V Server 2016
- Prepare to pass out the SAN (we have two ESXi diskless servers connected to an EMC array, going to Hyper-V with local storage)
- New network configuration (adding VLANs for a DMZ, a testlab, management interfaces... nothing fancy)
- New Active Directory domain/forest (we have a very old inherited domain that doesn't follow best practices)
- Upgrade from Windows Server 2008 R2 to Windows Server 2016
- Deploy standarized Windows (client and server) images using Microsoft Deployment Toolkit + WDS
- Manage software in client computers with Chocolatey
- Document everything (going with Dokuwiki)
- Try to automate everything as much as possible with Puppet (using The Foreman) and PowerShell/PowerShell DSC
So, I will be really busy for months...
Instead of analyzing all of the other things you have on your todo list, what you have here is a realistic starting point.
Take all of these things and start at the top and work your way down. I like the list in the order you have it
Thank you.
Also, I'm going to break my day in "project time" and "tech support time", because I'm neglecting my users too much ATM. Never a good thing.
-
@dashrender said in Seeking how to improve:
@manheraz said in Seeking how to improve:
@dashrender said in Seeking how to improve:
How about starting by sharing a list of your to dos, etc.
Well, that's one of my problems, trying to bite more than I can reallistically chew.
I have hundreds of items in my to do list, 90% "self imposed". As I keep learning, I keep adding ideas to improve the current infrastructure.
Then, I have a tought time trying to prioritize my work (too much items to process leads to something like analysis paralysis)
Also, trying to learn new technologies requires time, and that makes me question: should I improve my knowledge in the technologies in use at the moment or should I focus in learning more useful things for a near future?
Example: Should I improve my VMware skills (currently in production) or should I invest learning Hyper-V, PowerShell, PowerShell DSC, Puppet to be able to use that in a few months?
Our biggest project at this time is a total technology "refresh":
- Migrate from VMware vSphere Essentials to Hyper-V Server 2016
- Prepare to pass out the SAN (we have two ESXi diskless servers connected to an EMC array, going to Hyper-V with local storage)
- New network configuration (adding VLANs for a DMZ, a testlab, management interfaces... nothing fancy)
- New Active Directory domain/forest (we have a very old inherited domain that doesn't follow best practices)
- Upgrade from Windows Server 2008 R2 to Windows Server 2016
- Deploy standarized Windows (client and server) images using Microsoft Deployment Toolkit + WDS
- Manage software in client computers with Chocolatey
- Document everything (going with Dokuwiki)
- Try to automate everything as much as possible with Puppet (using The Foreman) and PowerShell/PowerShell DSC
So, I will be really busy for months...
As already mentioned by @dafyre, this is a pretty good list. I'd say because of this list, you've already dictated the path you need to take.
Should you bother with VMWare? Nope, you're company is moving away from it, it's useless knowledge at this point.
Your project list looks good. For each part of it, start a thread. It might be a good idea to start a thread first as a project over view - list the current environment, where you plan to go and why you choose that path. I'm sure this group will weigh in and perhaps help you tweak the path.
Thanks. Starting a thread for every project is a great idea.
I'm going to use Dokuwiki to plan and document my projects. I usually document how I did something, but I always forget to document why I plan it/did it that way.
That kind of details could be valuable when posting a new thread.
-
@irj said in Seeking how to improve:
Are you worried about improving just your skills or are you trying to improve your career and make more money?
I dont think a company of 60 employees has a very high ceiling for IT salary....
I just want to improve as an IT pro.
You are right, the spanish SMB market has very low salaries, but I'm fully aware of it and it's a trade for the flexibility and freedom that I really need right now.
-
@manheraz said in Seeking how to improve:
@irj said in Seeking how to improve:
Are you worried about improving just your skills or are you trying to improve your career and make more money?
I dont think a company of 60 employees has a very high ceiling for IT salary....
I just want to improve as an IT pro.
You are right, the spanish SMB market has very low salaries, but I'm fully aware of it and it's a trade for the flexibility and freedom that I really need right now.
And you get to live in Spain, which is worth an awful lot.
-
@scottalanmiller said in Seeking how to improve:
@manheraz said in Seeking how to improve:
Our biggest project at this time is a total technology "refresh":
- Migrate from VMware vSphere Essentials to Hyper-V Server 2016
- Prepare to pass out the SAN (we have two ESXi diskless servers connected to an EMC array, going to Hyper-V with local storage)
- New network configuration (adding VLANs for a DMZ, a testlab, management interfaces... nothing fancy)
- New Active Directory domain/forest (we have a very old inherited domain that doesn't follow best practices)
- Upgrade from Windows Server 2008 R2 to Windows Server 2016
- Deploy standarized Windows (client and server) images using Microsoft Deployment Toolkit + WDS
- Manage software in client computers with Chocolatey
- Document everything (going with Dokuwiki)
- Try to automate everything as much as possible with Puppet (using The Foreman) and PowerShell/PowerShell DSC
That's a lot, but sounds like a good, solid list of stuff to be doing.
Thanks, Scott.
Also, thank you for your posts on smbitjournal.com. They helped me a lot!
-
@manheraz said in Seeking how to improve:
@scottalanmiller said in Seeking how to improve:
@manheraz said in Seeking how to improve:
Our biggest project at this time is a total technology "refresh":
- Migrate from VMware vSphere Essentials to Hyper-V Server 2016
- Prepare to pass out the SAN (we have two ESXi diskless servers connected to an EMC array, going to Hyper-V with local storage)
- New network configuration (adding VLANs for a DMZ, a testlab, management interfaces... nothing fancy)
- New Active Directory domain/forest (we have a very old inherited domain that doesn't follow best practices)
- Upgrade from Windows Server 2008 R2 to Windows Server 2016
- Deploy standarized Windows (client and server) images using Microsoft Deployment Toolkit + WDS
- Manage software in client computers with Chocolatey
- Document everything (going with Dokuwiki)
- Try to automate everything as much as possible with Puppet (using The Foreman) and PowerShell/PowerShell DSC
That's a lot, but sounds like a good, solid list of stuff to be doing.
Thanks, Scott.
Also, thank you for your posts on smbitjournal.com. They helped me a lot!
Have you started watching the SAMIT videos, too? It's like SMBITJournal, but on youTube
-
@scottalanmiller said in Seeking how to improve:
@manheraz said in Seeking how to improve:
@irj said in Seeking how to improve:
Are you worried about improving just your skills or are you trying to improve your career and make more money?
I dont think a company of 60 employees has a very high ceiling for IT salary....
I just want to improve as an IT pro.
You are right, the spanish SMB market has very low salaries, but I'm fully aware of it and it's a trade for the flexibility and freedom that I really need right now.
And you get to live in Spain, which is worth an awful lot.
Yup! Not going to lie... I really love this country!
-
@scottalanmiller said in Seeking how to improve:
@manheraz said in Seeking how to improve:
@scottalanmiller said in Seeking how to improve:
@manheraz said in Seeking how to improve:
Our biggest project at this time is a total technology "refresh":
- Migrate from VMware vSphere Essentials to Hyper-V Server 2016
- Prepare to pass out the SAN (we have two ESXi diskless servers connected to an EMC array, going to Hyper-V with local storage)
- New network configuration (adding VLANs for a DMZ, a testlab, management interfaces... nothing fancy)
- New Active Directory domain/forest (we have a very old inherited domain that doesn't follow best practices)
- Upgrade from Windows Server 2008 R2 to Windows Server 2016
- Deploy standarized Windows (client and server) images using Microsoft Deployment Toolkit + WDS
- Manage software in client computers with Chocolatey
- Document everything (going with Dokuwiki)
- Try to automate everything as much as possible with Puppet (using The Foreman) and PowerShell/PowerShell DSC
That's a lot, but sounds like a good, solid list of stuff to be doing.
Thanks, Scott.
Also, thank you for your posts on smbitjournal.com. They helped me a lot!
Have you started watching the SAMIT videos, too? It's like SMBITJournal, but on youTube
Great tools for realizing what you don't know.
