Do I need to know what memory and CPU resources a Network Discover scan consumes, on the servers to be scanned?
Server 2019 running GSS 3.3 RU2
Problems after imaging
Any images that were created before the new server rebuild (last week of december) can be used to image a PC and it goes through the config, joins domain, completes tasks and works
Any new images (created since the rebuild – last 2 weeks) the image will create with no issues – but when pushed to any other PC, it images fine but stops at configuration point with no error (windows 10 1809)
When logging in locally it has a 169 internal network address
Checked drivers, uninstall, reinstall still no ip address, no issues in device manager, card reported as working (its as if it cant connect to DHCP server)
Tried using exisiting image create jobs and recreating the create job , tried pushing and pulling from different PCs but outcome is always the same – 169 address
Ive chekced everything I can think of and tried everything
Aside from reinstalling everything again on the server I was wondering if any body had any ideas ?
I have checked in the temp folder on express on 2 servers and only difference I cam see when comparing cfg files is a line
not working server line
Route0=0.0.0.0 ,0.0.0.0 ,10.110.1.250 , ,1, ,0,0
working server line
If this is the cuase im not sure where to make the changes to it?
We have 4 other servers on other sites, all identical and all working
We are testing SSL Inspection on UAT right know and I have question related to certificate which proxy send during SSl proccess. In default proxy send only emulate certificate is there any way to change that to send all Chain of certificate ? In this way we would not have to distribute certificate of proxy on all workstations because Sub CA whch certificate is signed na Root CA is trusted for users/coumputer in a AD domain.
I’ll be very grateful for your help
Hello, I have a Windows Server 2012 R2 server with GSS 3.3 installed. Client computer OS is Windows 10, Disk Management looks like this:
Create image command: -CLONE,MODE=CREATE,SRC=2,DST=%IMAGE_FILENAME% -SURE -IB -SPLIT=0 -Z3
Restore command: -CLONE,MODE=PRESTORE,SRC=%IMAGE_FILENAME%:4,DST=2:4 -sure
The create image job works fine. Restore image job also works for the first time but failed for the second time, job status displayed “Unable to boot to Windows automation”.
I searched a little bit in this Forum and found similiar posts, e.g.
For my situation, if the default boot setting is not correct initially, how the restore image job success for the first time? I am wondering, besides of checking boot order, is there any place I can check? Please advise, thank you in advance.
After some discussions with Symantec messaging teams, our business partners who are using Symantec Message Labs as their message filtering service have reported that the sender “Oaknorth.com” is blacklisted by Symantec Message Labs. This is resulting in some of the emails from our domain not getting delivered in the business partner environment.This is a whitelisting request to enable oaknorth.com and oaknorth.ai senders in your message filtering service. If you need any information, please let me know..
we have been experiencing problems with our mail server for a while, as it has been blacklisted by Symantec.
We are constantly checking our IP address (184.108.40.206) and it is considered with good reputation everywhere, except on Symantec.
Our customers keep complaining that their clients don’t receive their emails and we don’t understand why our server keeps being blacklisted.
Every day we use the IP reputation investigation tool, but everytime we check it again is blacklisted again and it doesn’t give us any reason.
Please help us removing our IP address from your blacklist or give us any hint on how to fix this problem.
Thank you in advance.