Posts made by pmoncho

pmoncho

@pmoncho said in Indentation Style:

Just wondering what many of the scripters and developers here like to use as their Indentation Style?

I was looking at my pretty messed up .PS1 scripts and trying to figure out which of the styles from https://en.wikipedia.org/wiki/Indentation_style
would make my scripts look more organized.

I find I am partial to Allman style. It seems that code blocks are more noticeable and finding a missing bracket seems easier.

wow - that's a lot of options.

I think I like whitesmith personally.

I didn't know till I looked also.

Whitesmith is nice too. Hmmm... decisions...decisions...

I am partial to using Tab's instead of space bar four times. Apparently this is a full-on debate about using Tab's that I did not know about either.

pmoncho

@phlipelder said in Random Thread - Anything Goes:

@dashrender said in Random Thread - Anything Goes:

@nadnerb said in Random Thread - Anything Goes:

So sad but true!

Why do so many companies have to hear it from an outsider before they believe it?

Prophet is never known as such in their own home land.

This is good. I have to remember this.

pmoncho

Just wondering what many of the scripters and developers here like to use as their Indentation Style?

I was looking at my pretty messed up .PS1 scripts and trying to figure out which of the styles from https://en.wikipedia.org/wiki/Indentation_style
would make my scripts look more organized.

I find I am partial to Allman style. It seems that code blocks are more noticeable and finding a missing bracket seems easier.

pmoncho

@dashrender said in Random Thread - Anything Goes:

@nadnerb said in Random Thread - Anything Goes:

So sad but true!

Why do so many companies have to hear it from an outsider before they believe it?

We will have your answer when we figure out why kids will listen to their friends and friends parents vs their own parents.

pmoncho

@dashrender said in CAL Counting:

@pmoncho said in CAL Counting:

@dashrender said in CAL Counting:

@pmoncho said in CAL Counting:

@dashrender said in CAL Counting:

@scottalanmiller said in CAL Counting:

@eleceng said in CAL Counting:

We will be using terminal services in a redundant setup so at least 10 RDS cals

Terminal SERVICES doesn't require more CALs when redundancy. But if you mean your TERMINALS (the thin clients) will be redundant, then it will.

One CAL gives you access to unlimited RDS servers.

RDS CALs are also concurrent, aren't they? Or did they change that?

Had this discussion a few years ago. From my understanding, RDS has a "pool" that grabs a license from the pool for each logged in user. It will re-up every 90 days each time the user logs in. So if you have multiple users that only log in once every 89 days, that can waste a ton of licenses, thus having to purchase more than actually is required.

Yeah, all that sounds familar - but don't new (users who haven't tried in the last 89 days) get a 90 temp license? So I would think/hope you wouldn't run afoul of the single off man off once in a while.

Found this:

https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-client-access-license

It looks like the temp license is only available in Device mode.

From the site you linked:

There is a licensing grace period of 120 Days during which no license server is required.

in combination with

Temporary RDS CALs are not available.

tells me each user likely gets a single 120 day grace, after which they will have to have a license.

this also seems newer than I recall.

RDS CALs are assigned to a user in Active Directory.

Does this mean it's not longer concurrent users? Once an RDS license is assigned, it's there for life? what happens when that user leaves the company?

And then we toss this on top of the pile.

I am unable to find anything specific from M$ but only the talk of others in forums stating that the license will go back into the pool after 90 days of no use.

So basically, we don't know. I have yet to run into this issue so I don't have first hand experience.

pmoncho

@dashrender said in CAL Counting:

@pmoncho said in CAL Counting:

@dashrender said in CAL Counting:

@scottalanmiller said in CAL Counting:

@eleceng said in CAL Counting:

We will be using terminal services in a redundant setup so at least 10 RDS cals

Terminal SERVICES doesn't require more CALs when redundancy. But if you mean your TERMINALS (the thin clients) will be redundant, then it will.

One CAL gives you access to unlimited RDS servers.

RDS CALs are also concurrent, aren't they? Or did they change that?

Had this discussion a few years ago. From my understanding, RDS has a "pool" that grabs a license from the pool for each logged in user. It will re-up every 90 days each time the user logs in. So if you have multiple users that only log in once every 89 days, that can waste a ton of licenses, thus having to purchase more than actually is required.

Yeah, all that sounds familar - but don't new (users who haven't tried in the last 89 days) get a 90 temp license? So I would think/hope you wouldn't run afoul of the single off man off once in a while.

Found this:

https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-client-access-license

It looks like the temp license is only available in Device mode.

pmoncho

@dashrender said in CAL Counting:

@scottalanmiller said in CAL Counting:

@eleceng said in CAL Counting:

We will be using terminal services in a redundant setup so at least 10 RDS cals

Terminal SERVICES doesn't require more CALs when redundancy. But if you mean your TERMINALS (the thin clients) will be redundant, then it will.

One CAL gives you access to unlimited RDS servers.

RDS CALs are also concurrent, aren't they? Or did they change that?

Had this discussion a few years ago. From my understanding, RDS has a "pool" that grabs a license from the pool for each logged in user. It will re-up every 90 days each time the user logs in. So if you have multiple users that only log in once every 89 days, that can waste a ton of licenses, thus having to purchase more than actually is required.

pmoncho

@eleceng said in CAL Counting:

@dashrender the organization already has user CAL's because all employees have email and can log in to the local computers, etc.

Do need user CAL's for every employee on every system or does 1 user CAL cover an employee on any and all systems corporation-wide?

One Windows Server User CAL covers one employee company wide.
You will also need a one Windows RDS User CAL for each user connecting to all RDS servers company wide.

pmoncho

@jimmy9008 said in What Are You Doing Right Now:

Turned down a job offer with a finance company. Better pay and benefits but I just did not feel excited for the position. Couldn't bring my self to sign the employment contract.

If your in the finance area, have you check out Upstart. They are hiring in multiple states and they also offer remote work.

pmoncho

@obsolesce

That is pretty cool. I will give that a try this morning.

pmoncho

@obsolesce said in Powershell split and sort date/time:

@pmoncho said in Powershell split and sort date/time:
@pmoncho

Small update - Changed code as I realized I had to build an additional array outside the foreach loop.
$taskserver = "RemoteSystem"
$tNames = "*Location*"

$taskList = (Get-ScheduledTask -CimSession $taskserver -TaskName $tNames)

$_taskListing = foreach ($task in $taskList){

        $tName = $task.TaskName
        $tNameXML = ($tName+".xml")
        $tPath = $task.TaskPath

        Get-ScheduledTaskInfo -CimSession $taskserver -TaskPath $tPath -TaskName $tName | Select-Object TaskName, NextRunTime
}
#check to see the array is sorting at least by TaskName
$_taskListing | Sort TaskName -Descending
on the last line, have you tried sorting by the next run time?

$_taskListing | Sort NextRunTime

I just got back here and yes, I did that and it does sort it correctly. I forgot I had it sorted by TaskName, changed it and it worked fine (after setting it as an array).

I would still like to figure out how to separate the Date and Time though. That way I can use the most recent start time and add 1 minute to it for the new task that will be created.

So, while I have the sort fixed, how the heck do I split it?

pmoncho

@pmoncho

Small update - Changed code as I realized I had to build an additional array outside the foreach loop.

$taskserver = "RemoteSystem"
$tNames = "*Location*"

$taskList = (Get-ScheduledTask -CimSession $taskserver -TaskName $tNames)

$_taskListing = foreach ($task in $taskList){

        $tName = $task.TaskName
        $tNameXML = ($tName+".xml")
        $tPath = $task.TaskPath

        Get-ScheduledTaskInfo -CimSession $taskserver -TaskPath $tPath -TaskName $tName | Select-Object TaskName, NextRunTime
}
#check to see the array is sorting at least by TaskName
$_taskListing | Sort TaskName -Descending

pmoncho

Powershell script to get a list of Scheduled Tasks on remote server, get the task info and then sort by NextRunTime then Name.

Reason is, I will have to create these same tasks in the future and want to offset the new tasks to start 1 minute after the last.

$taskserver = "RemoteSystem"
$tNames = "*Location*"

$taskList = (Get-ScheduledTask -CimSession $taskserver -TaskName $tNames)

foreach ($task in $taskList){
        $tName = $task.TaskName
        $tPath = $task.TaskPath

        Get-ScheduledTaskInfo -CimSession $taskserver -TaskPath $tPath -TaskName $tName | Select-Object TaskName, NextRunTime
}

Results in two columns:

TaskName          NextRunTime          

LOC TUL LAB    10/13/2021 7:01:01 PM
LOC TUL RT      10/13/2021 7:01:01 PM
LOC TPL LAB    10/13/2021 7:08:03 AM
LOC TPL RT      10/13/2021 7:00:25 PM
LOC RTL LAB    10/13/2021 7:06:06 AM
LOC RTL RT      10/13/2021 6:58:55 AM
LOC JRT LAB    10/13/2021 8:00:00 PM

How can I sort by the date / time column? I am stumped.

I looked up [datetime]::ParseExtract and Calculated properties but over my head when trying to use them.

pmoncho

@pmoncho said in Server upgrade advice for upgrade to ESXi 7.0 U3:

@jaredbusch said in Server upgrade advice for upgrade to ESXi 7.0 U3:

@pmoncho said in Server upgrade advice for upgrade to ESXi 7.0 U3:

BOSS card is out as it is a single CPU

What does the single CPU have to do with it?

Having only one CPU in a R440 does not power on ~~Slot II~~ Slot III on the motherboard. Therefore, there is no slot to put a BOSS card in.

Hmmm... now you have me thinking. Heading to look at the specs again to see exactly where the SD card is located.

*Edit - Changed Slot II to Slot III

The SD cards have their own slot. Bummer. No replacing it with the BOSS card.

pmoncho

@dashrender said in Server upgrade advice for upgrade to ESXi 7.0 U3:

@pmoncho said in Server upgrade advice for upgrade to ESXi 7.0 U3:

Oh also, the BOSS card is out as it is a single CPU and the Intel NIC is in the PCI slot.

I don't know the first thing about BOSS cards - what is it? and what does single CPU and a NIC in the PCI slot have to do with anything - unless that somehow implies that there is only one PCI slot and it's in use and BOSS is only PCI?

BOSS (Boot Optimized Storage System) Cards connect to PCI slot in the mother board. It holds two M.2 drives for a RAID 1 configuration to load the OS.

pmoncho

@jaredbusch said in Server upgrade advice for upgrade to ESXi 7.0 U3:

@pmoncho said in Server upgrade advice for upgrade to ESXi 7.0 U3:

BOSS card is out as it is a single CPU

What does the single CPU have to do with it?

Having only one CPU in a R440 does not power on ~~Slot II~~ Slot III on the motherboard. Therefore, there is no slot to put a BOSS card in.

Hmmm... now you have me thinking. Heading to look at the specs again to see exactly where the SD card is located.

*Edit - Changed Slot II to Slot III

pmoncho

@jaredbusch said in Server upgrade advice for upgrade to ESXi 7.0 U3:

use the boss card with dual nvme in raid 1 on all my new Dell servers.

That is the plan for all new systems now after discovering the debacle I am found myself in the last month or so. Just wish I was prescient two years ago.

pmoncho

@scottalanmiller said in Server upgrade advice for upgrade to ESXi 7.0 U3:

I think you listed the options and reasons. Now it is up to you how the time compares to the money in your situation.

Appreciate it. I kind of figured as the options are rather limited in this situation.

Using their workarounds to keep the SD Cards seems rather useless along with increased risk of future downtime IMHO.

pmoncho

@dafyre said in I can't even:

@pmoncho said in I can't even:

@gjacobse said in I can't even:

I. just. - ugh

This isn't a home, this is an office. ... ... ...

Dang, is it reverse day??? Weird.

Looks like the FB engineers got hold of the Speed knobs on his internet.

I don't think I have ever seen that before. I venture to believe it does not happen that often.

pmoncho

With ESXi 7.0 U3 SD cards/USB keys no longer recommended due to filesystem changes, I am wondering if anyone has other options than what I came up with.

Dell R440 with ESXi 6.7U3 and 16GB SD cards in RAID 1
Single CPU
Two 3.84TB RI SSD's in RAID 1 (Slot 0 and 1) on PERC H740P
Backplane has 10 2.5" drive slots (was on sale at Xbyte and cheaper than other options at the time)
Intel X710 SFP+ NIC

Will be upgrading soon to 7.0 U3 (waiting on Veeam) and plan to stop using the SD cards so the two options I can see are:

Purchase two Dell 120 or 240 GB SSD and make a separate RAID1 for OS install. Plop the two drives in slot 8 and 9, make RAID 1 and reload ESXI. I can then keep the data where it is.
Make multiple backups and export templates, Reconfigure current RAID and create two virtual drives, one being 80Gb and second being rest of the disk space.

I am leaning towards 1 as it will cost more in hardware but less in time. Option two is no extra hardware but a lot more time.

Any other thoughts?

Oh also, the BOSS card is out as it is a single CPU and the Intel NIC is in the PCI slot.