Jump to content
[[Template core/front/profile/profileHeader is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

Community Reputation

1 Neutral

My Information

  • Location
    Des Moines, IA
  • Agent Count
    > 6000 Agents
  1. I am curious to hear your insights @KKerezman - I have 10 years on Kaseya and am in the middle of transitioning to Automate....
  2. Following up on this as we have clients with strict egress and need to change from 8040/8041 to 443 and 80. Anybody have success in changing both settings? To clarify, we can move the Web Server to 443 with SSL but are having difficulty with the relay server going from 8041 to 80. Found a typo in the Web.Config - works without an issue now
  3. What does your LTErrors.txt file show for the communication?
  4. We are currently transitioning from Kaseya to Connectwise Automate..... We have the process in Kaseya and will be duplicating it in the next month in Automate but can give you an idea on our current process for local PC's: Create a local directory (planning on using C:\Windows\LTSvc\RapidFire) Download the data collector to that location from https://s3.amazonaws.com/networkdetective/download/NetworkDetectiveComputerDataCollector.exe Unzip the contents to the C:\Windows\LTSvc\RapidFire\NDCDC directory Execute shell command C:\Windows\LTSvc\RapidFire\NDCDC\nddc -local -silent -outbase %computername% -outdir Execute shell command C:\Windows\LTSvc\RapidFire\NDCDC\sddc -common -sdfbase %computername% -outdir Check for file NDCDC\%computername%.cdf and move to RapidFire root directory (C:\Windows\LTSvc\RapidFire) --Also check here as Rapidfire has change the default file creation location in the past: NDCDC\cdf\%computername%.cdf Check for file NDCDC\%computername%.sdf and move to RapidFire root directory (C:\Windows\LTSvc\RapidFire) Run a cleanup step to remove the downloaded exe and directories under the root *At this point, schedule or call the collector (which will require a valid Connector ID) https://s3.amazonaws.com/networkdetective/download/NetworkDetectiveConnector.zip -- As for running on the domain (we do not have that automated yet) just leave the files instead of running a cleanup on a DC and run the program manually. If someone has a recommendation for automating this I would be interested. A quick guess below: C:\Windows\LTSvc\RapidFire\NDCDC\NDDC\nddc -mbsa -updates -net -nonpingable -level2 -sql -ad -internet -speedchecks -eventlogs -dhcp -silent -outbase %computername% -outdir Check for file NDCDC\%computername%.ndf and move to RapidFire root directory (C:\Windows\LTSvc\RapidFire) Also grab the ndfRun.log and status-ndc.log my 2 cents - hope that helps!
  5. That's insightful @OmahaMCSE - Thanks!
  6. If you are going via command line then depending on the OS (32/64 bit): "c:\Program Files\Malwarebytes' Anti-malware\unins000.exe" /verysilent /suppressmsgboxes /norestart "c:\Program Files (x86)\Malwarebytes' Anti-malware\unins000.exe" /verysilent /suppressmsgboxes /norestart If they were installed via MSI you just need to identify the GUID and run: MSIEXEC /QN /X {Enter GUID Here}
  7. Have you thought about using the AutoAdminLogon registry key? or specify the DefaultUserName - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
×
×
  • Create New...