Been using the Linux version for ages. Now for win32 – even easier. VOIP + Analogue + digital tie lines = bye bye small business PABX.
I’ll review handsets later. Polycom and Zultsys are both great.
Geek Stuff
Been using the Linux version for ages. Now for win32 – even easier. VOIP + Analogue + digital tie lines = bye bye small business PABX.
I’ll review handsets later. Polycom and Zultsys are both great.
Hosts File
127.0.0.1Â Â Â Â Â Â config.messenger.msn.com
Blocks the SOAP config download for advertising.
Looks like one of my IS Staff is a Porn King – charges have been laid.
www.postcourier.com.pg/20060215/wehome.htm
www.thenational.com.pg/021606/nation19.htm
Not much to say in the way of “Good Taste”. 120KG mother of 8 is the star…..
Saw this in Exchange – System Manager | Tools | Monitoring and Status | Status – BNEMPS02 – In maintenance mode
Answer is here: http://hellomate.typepad.com/exchange/2004/03/exchange_in_mai.html
No need to stress
Google for Wireless Mesh and I’ll see you on the other side. These document authors REALLY need to look a the OSI Model and work out the difference between Layer 2 and Layer 3 technologies. Anyway – I highly recommend you read http://www.proxim.com/learn/library/whitepapers/mesh_primer_PP3-1005.pdf if you have an interest in setting up a Wireless Mesh. My definition of this is a number of Access Points covering an area that are NOT connected by Cat 5 to a backbone, but rather a multi-hop wireless, IN A SINGLE SUBNET. Proxim seems to be one of the few with a clue. Implementing solution atm – will advise results.
Update: A bit of a “discussion” later, and GFI has assisted my licensing problem. I suggest if you are using NSM to do Server monitoring, and want to ping everything with an IP too, you may want to talk to them. Those with pirated keys need not apply….
If you are installing DFS-R and see
“Event ID 6402”
The DFS Replication service failed to initialize replicated folder D:\Deployments\Install because the service detected that one of its private folders overlaps with an existing File Replication service (FRS) replica set. This is an unsupported configuration.
or
Event ID 6002
The DFS Replication service detected invalid msDFSR-Subscriber object data while polling for configuration information.
Then you need to make friends with ADSI Edit.
Mine was due to a badly removed FRS structure after I broke the root upgrading to Enterprise Edition (really wanted the extra savings on replication)
Under the Server Container for your server you’ll find the records for the old FRS replication that is conflicting – delete the references for all members (yeah – even DC’s, the DC records are housed elsewhere) and Bob’s your uncle. They are GUID looking thingies here.
Looks like one of my IS Staff is a Porn King – charges have been laid.
www.postcourier.com.pg/20060215/wehome.htm
www.thenational.com.pg/021606/nation19.htm
Not much to say in the way of “Good Taste”.
I like GFI – they make great products that fit mid tier companies (100 – 5000) perfectly, and they do it with better Microsoft integration than most – even better than MS themselves sometimes. BUT – this time they have stuffed up.
Network Server Monitor 7 – great product, doesn’t crash like 6.0. Price – you have to be kidding me – $1500 / 50 machines, no unlimted licences. That’s $1500 for 50 ping checks!!!!! Now I’ll pay $1500 for T/S logon checks, disk space, exchange services, HTTP file access, SQL queries etc etc etc. But for pinging my 120 switches – no way. For the $7000 bill total I’ll buy HP Openview. Sheesh.
BTW: 6.0 – Ping checks were FREE, and they had an “unlimited” licence.