Hi Justin,
Yes, the commands to do this are a little different. Here you go:

Stop the JDS Launch Daemon:
sudo launchctl unload /Library/LaunchDaemons/com.jamfsoftware.jamfdspolicy.plist

Make a backup of the apache config file: /Library/Server/Web/Config/apache2/sites/0000_any_443_.conf

Copy the backup the JDS made into the sites directory:
sudo cp /Library/JDS/conf/.0000_any_443_.conf /Library/Server/Web/Config/apache2/sites/0000_any_443_.conf

Remove the JDS binary and associated files:
sudo rm /Library/JDS
sudo rm /Library/LaunchDaemons/com.jamfsoftware.jamfdspolicy.plist
sudo rm /usr/sbin/jamfds

Hope this helps!

Are these commands the same under Ubuntu?

I don't see how they could be given some of the file locations are different, and for the most part, ubuntu distributions don't use launchd

it was more of a leading question hoping someone would chime in the file locations or commands needed for removal on linux.

JAMF posted this which seems to answer the question

https://jamfnation.jamfsoftware.com/article.html?id=339

Hey all,

In addition to the KB article linked above ("Components Installed on JDS Instances"), I've also posted a KB article on uninstalling a JDS instance:

https://jamfnation.jamfsoftware.com/article.html?id=340

Hope this helps.

-Erin

Thanks Erin!

There is an error in the KB for RHEL and Ubuntu in the removal:
Reads:
sudo rm /usr/local/jds
sudo rm /usr/local/sbin/jamfds

It should be:
sudo rm -rf /usr/local/jds
sudo rm -rf /usr/local/sbin/jamfds

As these directories are not empty.