dapaulio

what happens if you create a new SSID to test? does it connect if you have an open SSID?

I had this and fixed it by removing both KB's The symptoms will be WSUS Error: Connection Error when loading the console The event viewer will log an WSUS error with a load of SQL related information events KB3148812 was the original "fix" that broke wsus and was later pulled from wsus. KB3159706 was released to fix KB3148812 however if you are unlucky enough to deploy KB3159706 after KB3148812 was pulled from WSUS this also breaks wsus in the same way The Solution is to remove and decline both KB3148812 and KB3159706 then restart your server.

Good luck. Doesn't sound much of an issue if it is losing sync by 1 minute. Granted not ideal and it would probably bug me too but I think it only starts becoming a network issue if the time starts losing sync by several minutes Maybe put a ping dc -t on overnight see if you have any ping drops

Look at you stratum in the first. although your dc is configured as your time server your w10 computer appeared to look towards a reference time clock outside your network (stratum 1 - radio clock). whatever has happened between then and now it would appear now it is referencing your DC for a time (stratum 2 - (S)NTP). maybe your dc was not able to reply to the request at the time and moved onto a failsafe peer. who knows, im not exactly an expert in this area but i would start asking the question why is it not contacting my DC each time. there maybe underlying issues.

run on the affected machine W32TM /query /status /verbose look up last sync time then then go look any "system" event logs around that time that may help you relating to time-service

we deployed 2014 manually to a suite of 20. wasnt worth us bulking our image out for. seems ok on i3 4GB ram but i guess i never use it. there is a difference between just loading the software to see if it works and actually using the software but never receive any complaints. guess it would also depend on the patience and expectancy of your staff and students. our staff have come to terms that they are not likely going to get a whole new suite of i5/i7 computers loaded with 8GB+

never had a problem - are your clients configured with the correct time server and can you ping your ntp server - the group policy that specifies your time server has not got a WMI filter excluding your windows 10 clients to verify your time server w32tm /query /peers [/Code]

have you inadvertantly blocked the MAC addresses? couple things you could try - try spoofing the MAC address by changing the physical address option (not always called this) on the network interface properties. - remove your wirekess ssid from the laptop and reconnecting - in cmd netsh int ip reset c:\resetlog.txt netsh winsock reset

Before you continue ensure you understand what each line of code is doing to your server. Whilst fn-gn is probably upstanding gentleman that would not dream of harming anyones network it is very easy to tell someone in need to go run some code. It is good practice to make sure you understand what each line is doing. Once you are ok with this Type in ps to obtain your current ps executionpolicy Get-executionpolicy If the ps script is written correctly and assuming it is unsigned it could be the servers security policy blocking it from running The policy should be temporarily set to unrestricted. Run in ps Set-executionpolicy unrestricted Remember to set it back

Iv kniwn this to happen when techies have installed a piece of software that requires domain user credentials to export data to third party software eg AD or sims info. Have you used your credentials in any software services installed on your servers. If so you would need to change the password in the setting of every software you have used domain credentials If thus is the case I would ideally create a domain user account for each instance that software require domain level authentication. Lock it down so that it can only be used on the server installed on and document it

Also install smh which will report server and hardware status

Have you tried it. Although it isn't supported by hp doesn't mean it won't work. Depends how mission critical the server is. Granted if it were an important server you would stick to the supported guidelines but assuming that you are using an old g5 to fill a role says to me it all that important. We use to have a g5 that I played with and can't recall having any significant issues with it. I just installed straight from a dvd

I would run the PSP which will look at your current configuration and update any driver or firmware that is needed. Can I ask why you haven't installed 2012 r2. The support will be longer and will save you reinstalling the server when 2008r2 support ceases

We got a cheap mini display to vga for a surface pro and it worked fine. Cant see why usb to hdmi wouldnt. if i were in your position I would give the £3 a go. Even if it doesn't work its not going to break the bank

As suggested try downloading directly from the vendors website. eg realtek etc rather than toshiba's website Alternatively use an older version of the driver to see if that works

It is my understanding that anyone is allowed here and i welcome you, however you may find the majority of threads and the knowledgebase is orient around the education sector which can differ significantly on what the correct advice should be given, therefore may not be best place to seek answers to your questions. I think i understand your question. let me get this straight. you want to deploy a windows 10 image using the windows 7 OEM license and whether it is possible. in my opinion this would be a new install and not eligible for the free Windows 10 Upgrade Your reason for not obtaining a VLK is probably due to the fact that it seems senseless to pay for a w10 license when you have valid OEM licenses that grant you a free upgrade to W10. am i correct? Whilst i understand deployment would save you time over manual installation it is my understanding that WDS works in a domain environment using a VLK only. you may be able to deploy windows 10 on a generic key and manually enter the W7 OEM license displayed on the COA but that would take just as long and imagine you would need to manually activate through MS. Whilst a good way to save money i imagine MS have considered this and made it is illegal by their understanding to deploy using an OEM license. I hope i have understood your question EDIT: whilst writing this i stumbled across this http://download.microsoft.com/download/3/D/4/3D42BDC2-6725-4B29-B75A-A5B04179958B/Reimaging.pdf

Not particularly an expert in licensing. It bores the hell out of me and I will do my best to leave it to someone else if I can help it. Firstly what sort of organisation are you? This is my understanding of our licensing with in a school We are a school and have an ees agreement where we are issued a kms license key for each operating system to install on to a kms host server eg one for win 7 and one for win 10. This will then license all the computers that are connected to the domain. Ees agreement works on Full Time staff (FTE) which you can get from your business manager.

Anyone deployed marshmallow on to a sg s4 i9505? Currently running lollipop and it it really unstable and want to upgrade the os. Anyone have any good advice?

You could run diagnostics within sims which reports potential duplicates. Also reports on other potential issues like blank first name etc

anything interesting in the log just befor the crash? sh log EDIT: This may be better, shows recent first sh log -r

dont get me started. i look at ours and want to delete everything and start all over i have resources on staff shared duplicated in student shared and some resources date back as far as 2008

what was the issue then conflicting driver in the boot.wim? Glad you got it sorted

looks like we are getting somewhere

just to eliminate a faulty NIC have you tried deploying on another G3? you would be extremely unluck if you picked the only one wit a NIC fault Another suggestion is the NIC firmware upto date? It does sound like nothing more than a network driver issue so i would suggest installing windows manually from a cd. confirm the vendor and device id and go from there. thinking back i did actually have to do this for my G2's took me ages to find the correct driver, turned out that HP had the wrong driver for the hardware

maybe it is a conflicting driver? if you create a new windows 7 boot.wim and only inject the 400 G3 nic driver, does that work?