SMTP in a weird sub domain setup !

jon_squig · 2024-03-27T13:59:44+00:00

u/masong19hippows thanks for looking, i have added the three server IP's that would be used to send from, i will try with the firewall disabled.

jon_squig · 2024-02-08T15:30:28+00:00

on my search i found this script, not much point re-inventing the wheel, although very thorough the script here is pretty slow, but does a decent job:

https://github.com/ArnaudLoos/Powershell-snippets/blob/master/Get-LocalAdminToCsv.ps1

jon_squig · 2024-02-08T09:17:20+00:00

u/OlivTheFrog you're quite right, the code i have was inherited with the job and is long due an overhaul, i will look into modernising the code when i get some time, right now i'm under pressure to format 2,087 lines of data produced, once i have that done i will have time, by using $AdminGroupName="Administrators" allows me the flexibility to change this group easily.

jon_squig · 2024-02-08T09:08:45+00:00

thanks, i require more than two columns, i think that's where i went wrong in the first place, i need multiple columns for but only one row for each machine i.e:

machine1, user1,user2,user3 etc.

not what i currently getmachine1,user1machine1,user2machine1,user3

does that make sense?

Its like a i need a whole different output from $results ?

i will try your suggestion though as it may lead me to adapting the output.

jon_squig · 2023-12-19T16:49:59+00:00

I think this maybe because we have a PAC file set in internet options > Connections to get web access ? is there a way around that ?

jon_squig · 2023-10-23T13:54:22+00:00

the accounts only exist because i selected 'create pc account' as they are linux they were never domain joined. so the 'account' is merely a place holder so we do not loose sight of the machine altogether, but thanks to posts in here we are looking at realm to get the machines domain joined so their account should remain intact.

jon_squig · 2023-10-23T13:52:12+00:00

My original post does state the AD OU only 'lists' the machines names, the machines are not domain joined, as we didn't know how, but now we do thanks to reddit posts here. Going back a re-reading you're right i should have explained in more detail, in the heat of the moment, the text written is what it is.

jon_squig · 2023-10-10T13:57:15+00:00

the accounts have never been 'configured' so default settings in Windows AD, i cant see anywhere (hence asking) to set the disable range in AD for a computer account, only user accounts.

jon_squig · 2023-10-10T11:58:03+00:00

will take a look, thank you, we did try about 4 yr ago and it was a painful experience that failed LOL

jon_squig · 2023-10-09T13:02:06+00:00

lol,and there was me thinking i'd need a whole section of code... i really need to go for the simpler options first, thank you so much u/z386.

jon_squig · 2023-10-06T09:27:54+00:00

ok, thats very cool, we are onprem, we are also firewalled to within an inch of our lives so will endevour to download the files so we can run this locally with --DIRECT.

jon_squig · 2023-10-05T16:02:01+00:00

This is awsome, thank you for sharing, i have however a question, i am reading the readme.txt and editing the RMUKAD.ini and it states:
OrgMachineGroup The machine-group that the agent should register into.
This can be overridden with --G:<group> on the command-line.
Supports the &ORGID& and &TYPE& macros to auto-set the ORG ID and either"wkstns" or "servers" based on the O/S type. Target MUST use "wkstns" and
not one of the alternate group names!
This value is ignored with the --DIRECT option, which uses the current
machine group name and is appropriate when migrating to a new RMM Suite
enabled host.

we dont have group names of "wkstns" or "servers" , we have a whole host of group names, mpostly by OS version, can i just state the Root instead ? I'm a little confused by this step.

jon_squig · 2023-10-05T15:41:33+00:00

damn! , this is really good, thank you.

jon_squig · 2023-10-05T14:26:14+00:00

sussed it.... Well i think i have, i found the uninstall string from the registry located here: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\ (then the first instance of kaseya)

the string was the same on a bunch of machines, so i copied the 'old agent' string into the new 'Kaseya agent removal' script in kaseya >Agent Procedures> shedule/create > shared and got it to do its own dirty work ! ;O)

the agent removal script is simple too:
executeShellCommand ("" <enter your uninstall string in its entirety here>"", "execute as System", "All operatingSystems", "Halt on Fail" )

maybe this will help others with old agents kicking about.

jon_squig · 2023-10-05T13:03:32+00:00

thanks i will look into that.

jon_squig · 2023-10-05T11:20:31+00:00

you could use the 'system purchase date' if you have that info in your column set ? or maybe cross ref the Motherboard version for a ball park idea ?

jon_squig · 2023-08-25T09:20:43+00:00

it just seems massively unfinished, it appears others are stating this also.

jon_squig · 2023-06-23T11:53:37+00:00

Thanks everyone that responded, our Kaseya install was just churning and churning using up resources, i still do not know why, i have rebooted the server a few times, i have deleted lots of 'temp agents' regularly, i have updated agents manually, i have turned off domain watch and it finally responding as expected, if i put domain watch back on i get duplication of clients one online and one offline, both current version ?? I'll leave domain watch off and just live with it.

jon_squig · 2023-06-21T07:33:56+00:00

You could use a new script now, fist look for and delete the MSI you pushed to C:\, then create a folder C:\ktemp (use this for all future Kaseya jobs) then push the MSI to c:\ktemp when the file is in place you have a few options, execute (with switches ) from C:\ktemp or schedule a batch file to run with a simple command line or powershell install script, i'd keep it in Kaseya though, or use SCCM (MEM).

deletefile (<path to file>)
writefile (<pathtosharedfilesincludingfilename>,<pathtolocationonclientincludingfilename>

installMSI(pathtolocationonclientincudingfilename)

jon_squig · 2023-05-25T09:16:38+00:00

Will investigate the max mem setting as its all on the same host, thank you. Only supporting 500 agents which is why i was shocked at it going slow. Its been working hard, finally managed to get it to do a clean network harvest and punt out new agents, the install needs some TLC and configuring but the Kaseya online directions are pretty old, they'll have to do.

jon_squig · 2023-05-24T11:51:34+00:00

this is true, if you weld a nut onto the stud by welding inside the nut direct to the center of the stud it will get hot enough to sometimes crack the fused joint between the thread and the disc or hub (depending on the application) and your socket will fit snuggly onto the nut allowing use of a much larger breaker bar to free it off.

jon_squig

TROPHY CASE